When i run a build I'm getting an older version of the pipeline in the UI instead of the updated one. If i go to the legacy view of jenkins i see the updated version as expected. Some suggestionsabout this problem?
Related
I'm using SonarQube Enterprise 8.7 and running scans with it via Jenkins and I'm wondering if there's an option or parameters within SonarQube to have the name of my scanned branches displayed in the Jenkins UI.
This image is an example of what I'm after
The names have been blurred out but you can see the name digital which forms part of the branch name.
It seems to work straight out of the box with older versions of SonarQube, but not with newer versions.
Any ideas anyone?
Thanks.
I figured it out.
I just needed to add this to my Jenkinsfile and it works.
currentBuild.description=$BRANCH_NAME
I have started learning Jenkins recently.
I installed docker on a server which I created on AWS server and using docker I have installed Jenkins.
I wanted to test a Hello pipeline stage by creating new item, but when I go to the pipeline tab I cant see any options like pipeline script or pipeline script from SCM . I have installed git plugin and pipeline plugin also seems to be installed successfully. I am not able to continue my study further. I will be really thankful if someone can help me here.
In reality the pipeline plugin is not just one plugin but a bunch of 6 to 8 plugins. So you may want to install all the pipeline related items in your available plugins section of Manage Jenkins. Once this is done, a reboot of Jenkins is required for the changes to take effect. Here are some of them:
https://plugins.jenkins.io/build-pipeline-plugin/
https://www.jenkins.io/doc/pipeline/steps/pipeline-build-step/
https://plugins.jenkins.io/pipeline-stage-view/
I have a Jenkins system where I connect to slaves using a custom command which is run on master.
It seems that with version 2.89.2 this option has been removed from the UI, only allowing SSH, Java Web Start or Windows server.
Is this intentional? Is there a way to restore the previous behavior?
Thanks!
I was having this issue after the update as well - broke all my agents. Looking at the patch notes this is an intentional change, as the functionality has been moved into a new plugin:
https://plugins.jenkins.io/command-launcher
Installing this should restore the old behaviour.
I am using Jenkins 2.73.2 with Blue ocean 1.3.1 in the Linux Redhat. I wanted to build maven project located at GitHub repository. I have created a JenkinsFile for a blue ocean pipeline and recently updated it with some changes which were saved successfully on GitHub repository. But when I am running the pipeline again it is still running the old JenkinsFile.
So I checked the workspace of Jenkins and found that the folder for that pipeline was not updated and has old JenkinsFile which is causing this issue. Now I am stuck and don't know where did I go wrong or what I have missed in configuration/settings?
As susmit says in a comment,
This issue got resolved when I used the option available in the jobs where we can clear the workspace before running any jobs.
to avoid this problem you can use the option "Clear Workspace before running job" available in the jobs parameters.
I am using the most recent jenkins setup from https://cloud.google.com/tools/repo/push-to-deploy in order to CI my development environment codebase. I noticed that the jenkins git plugin in the image provided is out of date and seems to have a bug with regex branch matching. I updated the plugin to the latest version but after that it seems that jenkins will not restart.
Rebooting the server got jenkins back up, but the google startup script doesn't relaunch and reconnect the docker slave images properly.
Has anyone had this experience and resolved it?