I'm running Jenkins version 1.466.12.1 (Jenkins Enterprise 12.11). With a new job I'm trying to add a post-build action to build other projects, but the expect radio buttons for trigger options isn't there.
I have jobs that were already created that have the following options:
Trigger only if build succeeds
Trigger even if the build is unstable
Trigger even if the build fails
Those options don't exist if I create a new job. If I copy a job, then those options exist. I don't recall the version number of the previous Jenkins Enterprise, but it was working then.
I also have a non-enterprise version of Jenkins running on my desktop computer and those Trigger options don't exist on version 1.483.
Did something change with this post-build action? Maybe I forgot a fancy/useful plugin?
JENKINS-16444 was fixed in Jenkins 1.500. The workaround should be to add the build trigger, save the configuration, then go back to the configuration page again and these options should be visible—the problem applies only when first adding the trigger.
Related
Jenkins Version :- 2.319.1
I have upgraded Jenkins to 2.319.1 and after the upgrade now I am trying to make some modification in the freestyle job but the configuration page is scattered. Also, after making the changes when I try to click on "Apply and Save" button no action is performed from the Jenkins side. It doesn't save the changes while clicking on the "Apply and Save" button. No Error is displayed while trying to Apply the changes or trying to Save the changes in the Freestyle Jobs.
Was trying to modify the Old Freestyle jobs created on the previous Jenkins version and it should have allowed me to make the changes in the jobs but its not allowing me to make any modification to the existing jobs and also the UI is scattered for Freestyle Jobs configuration page.
We have some jenkins pipeline jobs defined with Jenkinsfile's located in bitbucket server, as described here. These builds are parameterized, and we'd like to be able to manually run them with non-default parameters.
The problem is, since the Jenkinsfile isn't checked out until we run it, the first time we run the build the build button is just "Build Now" instead of "Build with Parameters". Currently we are running it once with the default values so that it fails, and then running it again with the "Build with Parameters" button so we can pass in what we want.
Obviously not ideal. What is the right way to do this so we can run it with custom parameters the first time?
This is not possible currently, as they are post-processed they need to be executed in the 1st run before being known to jenkins and being available as 'Build with parameters'. Issue tracked here: https://issues.jenkins-ci.org/browse/JENKINS-41929
There are various ways to handle this,
The first is as you have alluded to, run it automatically/manually and let it fail, though maybe if you could set working defaults so it at least succeeds?
Another option, is to evaluate if this is the first run or not, and if so, execute the Jenkins job skipping all steps and purely processing the parameters.
I am trying to use the
Build after other projects are built
feature of Jenkins. I am using Jenkins ver 2.73.2 and whenever I go to
Configure job -> Build Triggers
and specify my projects, the configuration does not get saved. There is no save button so when I navigate to another page the configuration gets lost.
I am using JenkinsFile in all projects to build it so this is the first thing I am doing from the UI.
Couldn't find a proper solution to this issue anywhere.
Try to restart your jenkins.
Possibly you my have harmed you jenkins folder in program files.
Please try to upgrade your jenkins
I have some reports that I would like to push up to Github after my main project target builds.
These reports should be pushed up whether the first project succeeds or not. Can Jenkins do either of the following:
Specify multiple tasks (like Bamboo).
Build another project after the first, even if the first fails.
Reading your comment on the other Answers I propose this solution for you Jasper
Keep you existing project that builds and generates your reports and create a new project that you might call "report uploader" which only uploads your reports to your git.
1) Main Project Build
this will build you system, run it and test it (resulting in some reports, let's call them REPORT.o)
this project might or might not fail
REPORT.o should be archived as artifacts then the build is finished
the job should always trigger the "report uploader" job - Use the parameterized build trigger plugging
make sure this job has the checkbox wait for downstream jobs (else a new job might be started and overwrite the report files)
2) Report uploader Build
this will project will take arguments from the upstream job to find the artifacts
fetch them and upload them to whatever server you like to have
The same concept is loosely described on jenkins wiki
hope this fits your need
Yes.
With Git publisher you can push to a branch and choose whether or not to only do so when the build succeeds.
There is also a post-build action where you can build other projects and an option to do so even if the build fails.
Recently our organization decided to move from using Maven/Cargo-plugin to deploy our applications to using Puppet. We still have all of our builds and test jobs in Jenkins. So what I'm trying to figure out is how do I trigger a specific Jenkins job based on a specific line being changed in a puppet manifest? We are using a manifest that has all of our deployed components and their versions. If I change the version of one of the components, I want a specific test job to be triggered based on which component was changed. And eventually I will want to rollback the puppet change if the test fails. Has anyone done something related?
I haven't used it for your specific use case, but for a "pull" scenario where you want to monitor the contents of the Puppet manifest for changes, the Jenkins FSTrigger plugin should work for you as long as your Jenkins job can access the Puppet manifest file. You can set it up to look for changes in the entire file content, or just in a particular part of the contents.
If you want a "push" scenario to trigger a build as soon as the Puppet manifest is changed, you could write a script that runs after the changes are saved, checks which components have been changed, and triggers a build via the Jenkins CLI.