I have a runbook in Octopus which has had process steps added gradually over the past year. Is it possible to obtain Octopus audit logs (Configuration>Audit) which are filtered by each time that a step was added to the runbook, so that I can track who added it?
Related
I am using below API to get the latest deployment status(If any release going on) from 3 pipeline's before starting an deployment in each pipeline.
"https://vsrm.dev.azure.com/ABC/DEF/_apis/release/deployments?definitionId=100&deploymentStatus=inProgress"
"https://vsrm.dev.azure.com/ABC/DEF/_apis/release/deployments?definitionId=101&deploymentStatus=inProgress"
"https://vsrm.dev.azure.com/ABC/DEF/_apis/release/deployments?definitionId=102&deploymentStatus=inProgress"
Based on count I am deciding whether the any run going on in pipeline if count > 0. I am working on logic where if any deployment going on in other pipeline then Deployment should wait for other to finish since all are deploying to same environment.
The status checking task also is in progress so it is going to infinite loop to wait if task is running. Is there any way to achieve this.
Based on your requirement, you need to check the Deployment status of the release pipeline.
To alleviate your issue, I suggest that you can add an additional stage to each release pipeline and then you can add the check deployment status in the new stage.
Refer to my steps:
Add a new stage before the deployment stage and add the status check steps.
In the Rest API, you can add the definitionEnvironmentId parameter in the URL to check the specify stage.
For example:
"https://vsrm.dev.azure.com/ABC/DEF/_apis/release/deployments?definitionId=102&deploymentStatus=inProgress&definitionEnvironmentId=xx"
In this case, you can separate the check status step and the deployment process.
For more detailed info, you can refer to this doc: Deployments - List
I have a jenkins server on Openshift, The server goes down during the build even
after upgrading my plan to the bronze plan and using a large gear.
Each time I run a jenkins build on Openshift I get this message in the middle of the build:
The server is temporarily unable to service your
request due to maintenance downtime or capacity
problems. Please try again later.
And then the build disapear from the build history.
Is there a way to know why jenkins goes down during the build ? which logs should I check ?
I set the Builder size to large and the Builder type to jbossas-7, is there a better configuration to use to be able to finish the build?
Is there a way to set my maven repository in the slave so I can save some of my disk quota ?
In advance,Thanks.
Is it possible for the Atlassian Bamboo's administrator to create a default stage and have it automatically added to all the build plans( both existing and new build plans ) ? This stage should be read only to the users, meaning they should not be able to modify this stage.
This feature will let the administrator do certain house keeping things on the bamboo agents each time a new build job starts running on the agent.
I tried to search for it in the Atlassian's documentation but could not find anything as such.
We are talking about two things: a) stage Level Permission , b) adding one default stage to all plans.
Adding one default stage to all plans: You can create one template plan with default stage and permission. Every time a new plan creation request comes, you can just clone this template plan and add additional steps/repos etc. But for already existing plans, you will have to modify them individually.
Whereas I know, Bamboo provides plan level permission. You can give View/Build permission to users and Edit/Clone type of permissions to Bamboo administrators.
In your scenario, is user allowed to edit other stages except default stage?Why do you want user to be able to edit Build Plans?
I have a Build & Deploy Pipeline in Bluemix, I would like to create a condition where, if the build fails, it will automatically assign a defect (i.e., work item in the "Track & Plan" page) to whoever delivered the very latest change (or just assign to the main owner of the App/Project), also, if the build is completed successfully, I would like to tag it.
Tagging is ok, that's general GIT knowledge, I just wanted to solve 2 Problems with that plan:
How do we trigger a specific subsequent Stage in the pipeline if the current build fails/passes?
How do I create a work item from the pipeline? Do I need to create a separate GIT repo and build some sort of API package that allows me to invoke a mechanism that creates the ticket?
I guess I'm going too maverick with this Pipeline, please share your thoughts.
As of right now you can not create a work item from the pipeline. That is a great feature improvement and I can take it back to the team.
For your question about triggering a stage if something passes or fails... The way it works now only the next stage will be triggered if the previous is successful. The pipeline is based on Jenkins and Jenkins doesn't allow you to trigger a specific job if a job passes or fails. You would want to detect the pass or fail in your stage and do your logic based on that.
With the Hudson or Jenkins continuous integration servers, when a build is triggered either by an anonymous user, or by the CI server polling the repository, a pseudo-user is created with the data scraped from the commit information of the last commit.
How do I prevent this, as it's cluttering the list of registered users? I try to default to using post-receive hooks for scheduling builds, but for some repositories (e.g. those hosted by SourceForge), this is not an option as the machine running the repository is prevented from accessing external URLs
You can't prevent these from being created, as they are involved with how Jenkins logging and tracking works. However, if you need to see a list of only "real" users, you can do this easily by going to manage jenkins/manage users - users that lack a login will not appear.