Pipeline stage ID doesn't follow the stage when reordered

[Peder Alm]

I'm using the Jenkins pipeline stage view plugin REST API. When I use the 
path "/job/:job-name/wfapi/runs" I get a list of the last jobs.


Yesterday I renamed all the stages and also changed the order of the stages 
a bit. Here is a part of the JSON file, #152 is before the change and #153 
is after:


"name": "#153",
  "id": "6",
  "name": "Compile",
  "id": "13",
  "name": "Flash image",
  "id": "19",
  "name": "Generate log",
...
"name": "#152",
  "id": "6",
  "name": "1. Compile",
  "id": "13",
  "name": "2. Flash image",
  "id": "19",
  "name": "3. Prepare hardware",
  ...
  "id": "31",
  "name": "6. Generate log",


What I feel is very strange is that the *"Generate log"* stage in *#153* 
has taken over the stage id* 19* from *"3. Prepare hardware"* in *#152* 
(*"Generate 
log"* failed so I don't have any id number for *"Prepare hardware"* that 
comes later in the pipeline). I thought that the id was unique for a stage 
setup and that the id would change if you change the stage settings more 
than just renaming it.


My goal is to gather statistics over failed stages. But if the id isn't 
following the stages when I reorder them I don't know how to distinguish 
one test from another. Well, as long as I don't rename the stages I can use 
the name as my unique identifier, but that seems not so smart.


Does anyone have some solution for this or information about how the stage 
id tag works?


Version of my pipeline plugins (not the latest):

Pipeline: Declarative v1.1.9
Pipeline: Declarative Extension Points API v1.1.9   
Pipeline: Groovy v2.39  
Pipeline: Job v2.12.2   
Pipeline: Multibranch v2.16 
Pipeline: Nodes and Processes v2.13 
Pipeline: Supporting APIs v2.14

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d82e975d-60e5-4e12-8741-417d4eb16ee3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to find Browser version via Batch command

[LnT]

Hi -

I have 20 Windows VMs and 8 Suse Linux VMs - created slave nodes for a 
jenkins master.
20 Windows VMs containing Win7,Win8 & Win10 of both 32 and 64 Bit.

Requirement  : from the command prompt , need to find out the Browser 
version of Internet Explore , Mozilla firefox and Google Chrome.
What is the best way to get it via commands?

Regards,
LnT

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ecd475ba-42bd-4f9c-a38f-2d540860c267%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Multibranch pipeline / Gitlab integration: tag push events

[Samuel Mutel]

Hello,

I would like to know if someone has already setup the multibranch pipeline 
and the gitlab integration to start a job when a tag is pushed?

I setup the integration in GITLAB project, I setup also the multibranch 
pipeline. When a code is pushing to the master branch, it is working fine.
But if I create a new tag and push it. It is created in the tag tab in 
multibranch pipeline but the job is not started automatically.

Any idea?

Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0ed526be-2644-4ece-9304-db44c30628b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch pipeline / Gitlab integration: tag push events

[Samuel Mutel]

https://issues.jenkins-ci.org/browse/JENKINS-45838

Le jeudi 29 mars 2018 14:13:35 UTC+2, Samuel Mutel a écrit :
>
> Hello,
>
> I would like to know if someone has already setup the multibranch pipeline 
> and the gitlab integration to start a job when a tag is pushed?
>
> I setup the integration in GITLAB project, I setup also the multibranch 
> pipeline. When a code is pushing to the master branch, it is working fine.
> But if I create a new tag and push it. It is created in the tag tab in 
> multibranch pipeline but the job is not started automatically.
>
> Any idea?
>
> Thanks.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c7de01a1-a87e-43c4-93d6-9072864b8567%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins memory leak issue

[chicago]

> attaching few screenshot for same 

For future messages, I'd appreciate a concise description of the screenshot in 
text form. Thank you. 

Sincerely, 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D7CFD608-8736-4871-B6EB-8D4F9DDB2A61%40airmail.cc.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: Groovy script to do jenkins configuration on Manage Jenkins level for Blackduck detect plugin

[Sabyasachi Das]

Thanks Ewelina,

Actually we are looking for a method to retrieve the class instance which 
is keeping the BlackDuckHub configuration on master level.

 

For example for SonarQube it will be

 

import jenkins.model.Jenkins;

import hudson.plugins.sonar.SonarGlobalConfiguration;

import hudson.plugins.sonar.SonarInstallation;

 

def sonarDescr = 
jenkins.getInstance().getDescriptorByType(SonarGlobalConfiguration)l

sonarDescr.setInstallations(

new SonarInstallation(

'sonar',

'http://sonarqube.com',

// Other constructor properties...

)

);

sonarDescr.save();


Didn't find it in this class.

On Monday, March 26, 2018 at 10:54:17 PM UTC+5:30, Ewelina Wilkosz wrote:
>
> I haven't tried that and don't know the plugin, but I think you need to 
> find descriptor first
> since I've found global.jelly for DetectPostBuildStep (
> https://github.com/jenkinsci/blackduck-detect-plugin/blob/master/src/main/resources/com/blackducksoftware/integration/detect/jenkins/post/DetectPostBuildStep/global.jelly)
>  
> I would risk and say it may be that one: 
>
> https://github.com/blackducksoftware/blackduck-detect-plugin/blob/9993e4a22bf375c11d1872e4d619b83940b7e777/src/main/java/com/blackducksoftware/integration/detect/jenkins/post/DetectPostBuildStepDescriptor.java
>
> you can see there are public setters in it, so getDescriptor for 
> com.blackducksoftware.integration.detect.jenkins.post 
> (I guess) and use it to call setters
> does it make sense to you?
>
> In the future, hopefully, Jenkins Configuration as Code Plugin will be 
> able to take care of that for you :)
>
> On Monday, March 26, 2018 at 5:50:54 PM UTC+2, Sabyasachi Das wrote:
>>
>> Hi All,
>>
>> I have installed Blackduck detect plugin in jenkins. I want to do 
>> Blackduck  detect configurations via groovy script.
>>
>> I am able to do using GUI Manage Jenkins -> configure system but need to 
>> do similar activity via groovy script.
>> Similar configurations for other plugins can be done for example below. 
>> But for BlackDuck detect I cant find any appropriate class to provide.
>> https://github.com/blackducksoftware/blackduck-detect-plugin
>>
>> Anyone please help me on this.
>>
>> Thanks,
>> Sabya
>>
>> Sonar Script
>> ==
>> import jenkins.model.*
>> import hudson.plugins.sonar.*
>> import hudson.plugins.sonar.model.*
>> import jenkins.plugins.slack.SlackNotifier
>> import jenkins.plugins.git.GitSCMSource
>>
>> def inst = Jenkins.getInstance()
>>
>> def desc = inst.getDescriptor("hudson.plugins.sonar.SonarPublisher")
>> //or slack or git
>> def slack = instance.getDescriptor(SlackNotifier)
>> def gitPluginSetup = instance.getDescriptor(GitSCM)
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/06a99280-0b86-4d09-b0b9-4e4b5262da78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build on Nuget updates: does not seem to trigger using Generic-Artifactory Integration...

[Peter Swallow]

Did you ever resolve this?

The documentation for the nuget plugin is non-existant. I can't even get it 
to run the "Nuget Trigger Polling" once.

On Tuesday, 11 October 2016 23:52:11 UTC+1, RiRL wrote:
>
> I have setup a project to trigger "Build on NuGet updates" with a schedule 
> like [H/5 * * * *]; e.g.: every 5 minutes.
>
>
> I have configured Artifactory as the NuGet package server by setting the 
> Artifactory deployment server (note: another Jekins project successfully 
> populates NuGet packages to this server using a Target repository -- this 
> works fine, I can see the packages there in the Artifactory WebUI...)
>
> In the job I want to trigger on a nuget update, I have specified the 
> Resolution Details to the same deployment server and have configured the 
> Resolved Artifacts (yes we are using Artifactory Professional) and given 
> the reference to the repository, file pattern, and build informaton with 
> the mapping to the workspace.
> (note: this runs fine if I push the Build Now button... its fetches the 
> corresponding artifact(s) into the Jenkins workspace, as expected).
>
> However, despite the fact that I see updates to the Nuget Trigger Log, the 
> project does not run when there is (in fact) and update to the Nuget 
> package (as defined in the section immediately above).
>
> Anyone have any suggestions?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/af5077fc-2e49-40c6-98fc-d602f03d26f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Trend Graph

[Dan]

Jenkins uses a trend graph to display things like failed unit tests or 
compilation warnings as a function of build number. Is there a way to 
suppress only the first build OR to limit the height of the y-axis?

*My company's workflow*
- create a copy of a Jenkins job for your particular branch
- Build the branch without changes. This gives a baseline for the # of 
warnings in the code (it has very old code, so there are a LOT)
- The branch then automatically builds daily. New warnings introduced by 
the developer show up in the Trend Graph.

The Trend Graph is configured to show only new or fixed warnings.
The problem is that the 1st build introduces a ton of "new" warnings. This 
pushes the +Y-axis max value to >1000. Any warnings fixed/introduced after 
that are not visible.

*Solution*
If we could somehow suppress showing just that first build, while still 
showing all subsequent builds, this would be fixed. Or, if the +Y-axis 
could be limited to show numbers from 0-100, this would be fixed.

Is this possible?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9449eb64-eb32-4d86-ab8f-ace4a11ff4a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Web Start is working but jenkins says “Ping response time is too long or timed out”

[red 888]

I can successfully start the connection from the slave with this command:

java -jar agent.jar -jnlpUrl 
https://myserver:/computer/myslave/slave-agent.jnlp -secret sdfsdfsdf 
-workDir "c:\jenkins"

It start, it runs, it logs 0 errors, I do netstat on the master and see the 
connection is established.

But it says its offline with the error "Ping response time is too long or 
timed out"

The error itself is troubling because the whole point of web start is so 
the master doesn't need direct access to the slave. Is it actually trying 
to icmp to the slave?

The slave can only access the master over port .

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/57a3cd15-01a6-4126-af76-dcbad253a89a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

"Restrict where this project can be run" job configuration option has disappeared

[danielp]

Our team recently noticed that the job configuration option "Restrict where 
this project can be run" has disappeared. We're running the latest 
jenkins/jenkins:lts image (v2.107.1), in Docker. The option seems to be 
globally missing; I can no longer see it in any of the jobs I've looked 
through.

Our setup has had several slaves running with label use to constrain where 
jobs run for quite some time and the option was always there until 
recently. Despite not being visible, the jobs still seem to be constrained 
by the labels previously enumerated. I haven't found anything in the logs 
that would indicate a problem.

 Is anyone else seeing this? Any suggestions on how to isolate the problem 
and find a resolution? This looks like a bug, but I wanted to bounce it off 
the community first before creating an issue.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/bb1617e1-9440-42fa-a73c-7e534ce395b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trend Graph

[Mark Waite]

What if the first build on a branch were run without calculating warnings
(since you intend to ignore warnings from the first build, you could choose
not to compute those warnings and not to report them.

After first build is complete, reconfigure the job (Jenkins UI or in the
Jenkinsfile if Pipeline) to report warnings.

Mark Waite

On Thu, Mar 29, 2018 at 12:26 PM Dan  wrote:

> Jenkins uses a trend graph to display things like failed unit tests or
> compilation warnings as a function of build number. Is there a way to
> suppress only the first build OR to limit the height of the y-axis?
>
> *My company's workflow*
> - create a copy of a Jenkins job for your particular branch
> - Build the branch without changes. This gives a baseline for the # of
> warnings in the code (it has very old code, so there are a LOT)
> - The branch then automatically builds daily. New warnings introduced by
> the developer show up in the Trend Graph.
>
> The Trend Graph is configured to show only new or fixed warnings.
> The problem is that the 1st build introduces a ton of "new" warnings. This
> pushes the +Y-axis max value to >1000. Any warnings fixed/introduced after
> that are not visible.
>
> *Solution*
> If we could somehow suppress showing just that first build, while still
> showing all subsequent builds, this would be fixed. Or, if the +Y-axis
> could be limited to show numbers from 0-100, this would be fixed.
>
> Is this possible?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/9449eb64-eb32-4d86-ab8f-ace4a11ff4a4%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGfLMfX6P_ampCegh1aKTs5uU%3D9Lt67Ag97fQApE%2BaheQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: "Restrict where this project can be run" job configuration option has disappeared

[Daniel Beck]

> On 29. Mar 2018, at 21:10, dani...@gradecam.com wrote:
> 
>  Is anyone else seeing this? Any suggestions on how to isolate the problem 
> and find a resolution? This looks like a bug, but I wanted to bounce it off 
> the community first before creating an issue.

Check the log for relevant looking messages (mostly startup and while loading 
the job config form).

Also, output of `Jenkins.instance.labels.size()` and 
`Jenkins.instance.clouds.size()` in the script console would be interesting.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6654C50B-44D8-4CF1-AF9D-301768FE8E5E%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

How to get username of users logged in jenkins in logs?

[payal halder]

How to get username of users logged in Jenkins in logs?
Audit Trail plugin is not helping with username

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/81d21ca4-fea0-4e1b-8228-c4bf2dd79388%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trend Graph

[Ullrich Hafner]

I think this will not work. If no previous result is found, then an empty set 
of warnings is used as baseline, so we still get a large number of new 
warnings. I wonder if it would make sense to change the current behavior of my 
plugin. I must admit that marking all warnings of the first build as new is not 
a conscious decision. Maybe I should change that so that the first build always 
has no new warnings. What do you think? I’m not sure if I break something from 
other peoples’ jobs if I change that…

The other suggestions about changing the graphs: this is currently not 
supported will will never be supported with the current chart implementation. 
In the future (*), I would like to replace the png server side rendered charts 
with client side rendered JS charts. Then it should be easy to configure these 
graphs on the client side.

(*) Currently this is blocked by an integration of an old Prototype.JS library 
in Jenkins core, see https://issues.jenkins-ci.org/browse/JENKINS-49319 for 
details

> Am 29.03.2018 um 21:42 schrieb Mark Waite :
> 
> What if the first build on a branch were run without calculating warnings 
> (since you intend to ignore warnings from the first build, you could choose 
> not to compute those warnings and not to report them.
> 
> After first build is complete, reconfigure the job (Jenkins UI or in the 
> Jenkinsfile if Pipeline) to report warnings.
> 
> Mark Waite
> 
> On Thu, Mar 29, 2018 at 12:26 PM Dan  > wrote:
> Jenkins uses a trend graph to display things like failed unit tests or 
> compilation warnings as a function of build number. Is there a way to 
> suppress only the first build OR to limit the height of the y-axis?
> 
> My company's workflow
> - create a copy of a Jenkins job for your particular branch
> - Build the branch without changes. This gives a baseline for the # of 
> warnings in the code (it has very old code, so there are a LOT)
> - The branch then automatically builds daily. New warnings introduced by the 
> developer show up in the Trend Graph.
> 
> The Trend Graph is configured to show only new or fixed warnings.
> The problem is that the 1st build introduces a ton of "new" warnings. This 
> pushes the +Y-axis max value to >1000. Any warnings fixed/introduced after 
> that are not visible.
> 
> Solution
> If we could somehow suppress showing just that first build, while still 
> showing all subsequent builds, this would be fixed. Or, if the +Y-axis could 
> be limited to show numbers from 0-100, this would be fixed.
> 
> Is this possible?
> 
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/9449eb64-eb32-4d86-ab8f-ace4a11ff4a4%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> 
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGfLMfX6P_ampCegh1aKTs5uU%3D9Lt67Ag97fQApE%2BaheQ%40mail.gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/80A72BD9-B8BB-46C1-B747-CC1EF297ADC8%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

withMaven triggers same project?

[Dan Tran]

Hi 

I am finally able to get a project to trigger a downstream project belong 
to the same multi-branch projects 

However, I now facing a strange situation where the downstream project 
triggers itself in a loop. 

It may have something to do with my downstream project with multiple 
withMaven invocations

The correct solution would be for the withMaven plugin not to trigger the 
same project.

is it reasonable to ask?
.
Thanks

-Dan

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/de8519e7-809a-4cb2-bcb7-86db1dbfdade%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.