[JIRA] [build-name-setter-plugin] (JENKINS-22079) Enable build parameters to be used in build name

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin commented on  JENKINS-22079 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Enable build parameters to be used in build name  
 
 
 
 
 
 
 
 
 
 
Build parameters are passed as environment variables so you could use them just write: $ {ENV, var="parameter_name"} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-name-setter-plugin] (JENKINS-22079) Enable build parameters to be used in build name

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin started work on  JENKINS-22079 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-name-setter-plugin] (JENKINS-22079) Enable build parameters to be used in build name

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin edited a comment on  JENKINS-22079 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Enable build parameters to be used in build name  
 
 
 
 
 
 
 
 
 
 Build parameters are passed as environment variables so you could use them just write:  ${ENV, var="parameter_name"} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-name-setter-plugin] (JENKINS-22079) Enable build parameters to be used in build name

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin edited a comment on  JENKINS-22079 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Enable build parameters to be used in build name  
 
 
 
 
 
 
 
 
 
 Build parameters are passed as environment variables so you could use them just write:  ${ENV, var="parameter_name"} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-name-setter-plugin] (JENKINS-22079) Enable build parameters to be used in build name

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin assigned an issue to Lev Mishin 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-22079 
 
 
 
  Enable build parameters to be used in build name  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi Lev Mishin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [memory-map-plugin] (JENKINS-29804) Parse error on comments in linker file (GCC) (Praqma case 13367)

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29804 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Parse error on comments in linker file (GCC) (Praqma case 13367)  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jan Krag Path: .gitignore src/main/java/net/praqma/jenkins/memorymap/parser/gcc/GccMemoryMapParser.java src/main/resources/net/praqma/jenkins/unit/prom.ld src/main/resources/net/praqma/jenkins/unit/prom.map src/test/java/net/praqma/jenkins/unit/MemoryMapGccParserTest.java src/test/resources/net/praqma/jenkins/unit/prom.ld src/test/resources/net/praqma/jenkins/unit/prom.map http://jenkins-ci.org/commit/memory-map-plugin/abb0de1466a15948eabbd3b87cb14432f8569108 Log: JENKINS-29804 Strip C-style block comments from memory config files before parsing 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [memory-map-plugin] (JENKINS-29052) Plugin fails when defining a graphless parser (our case 13212)

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29052 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Plugin fails when defining a graphless parser (our case 13212)  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Thierry Lacour Path: src/main/java/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser.java src/test/java/net/praqma/jenkins/integration/JENKINS_29052_IT.java http://jenkins-ci.org/commit/memory-map-plugin/5eeaed1bacc77263f2d51f1c1b6d108a671c532b Log: Fixed JENKINS-29052 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [other] (JENKINS-30958) Slaves using 10 executor whereas specified 4

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30958 
 
 
 
  Slaves using 10 executor whereas specified 4  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

Component/s:
 
 other 
 
 
 

Component/s:
 
 _test 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [slack-plugin] (JENKINS-29696) Slack notifications are serialized

[sam.mxra...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Gleske commented on  JENKINS-29696 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Slack notifications are serialized  
 
 
 
 
 
 
 
 
 
 
Merged and possibly fixed in the 2.0 release. https://github.com/jenkinsci/slack-plugin/pull/122 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [slack-plugin] (JENKINS-30559) Option to omit commit messages from a notification message

[sam.mxra...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Gleske edited a comment on  JENKINS-30559 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Option to omit commit messages from a notification message  
 
 
 
 
 
 
 
 
 
 Merged and possibly fixed in the 2.0 release.   https://github.com/jenkinsci/slack-plugin/pull/133 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [email-ext-plugin] (JENKINS-30854) Support AWS SES Message IDs for In-Reply-To header

[devnull.jenk...@molb.org (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Johannes Weißl commented on  JENKINS-30854 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support AWS SES Message IDs for In-Reply-To header  
 
 
 
 
 
 
 
 
 
 
I added a paragraph to https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+Recipes#Email-extRecipes-PostsendScripts 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [memory-map-plugin] (JENKINS-30000) Refactor Texas Instruments Parser (Part one) (Praqma case 13215)

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-3 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Refactor Texas Instruments Parser (Part one) (Praqma case 13215)   
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Thierry Lacour Path: .gitignore README.md check_for_changelog.rb pom.xml src/main/java/net/praqma/jenkins/memorymap/MemoryMapBuildAction.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapDslExtension.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapGraphDslContext.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapJobDslContext.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapParserDslContext.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapProjectAction.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapRecorder.java src/main/java/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration.java src/main/java/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfigurationDescriptor.java src/main/java/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/GccMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/KeilMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapConfigFileParserDelegate.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapMapParserDelegate.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapParsable.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapParserDescriptor.java src/main/java/net/praqma/jenkins/memorymap/parser/TexasInstrumentsMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/gcc/GccMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/ti/TexasInstrumentsMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapConfigMemory.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapConfigMemoryItem.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapGroup.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapParsingResult.java src/main/java/net/praqma/jenkins/memorymap/util/FileFoundable.java src/main/java/net/praqma/jenkins/memorymap/util/HexUtils.java src/main/java/net/praqma/jenkins/memorymap/util/MemoryMapError.java src/main/java/net/praqma/jenkins/memorymap/util/MemoryMapFileNotFoundError.java src/main/java/net/praqma/jenkins/memorymap/util/MemoryMapMemorySelectionError.java src/main/resources/net/praqma/jenkins/memorymap/MemoryMapProjectAction/floatingBox.jelly src/main/resources/net/praqma/jenkins/memorymap/MemoryMapProjectAction/index.jelly src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/config.jelly src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-chosenParser.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-graphConfiguration.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-scale.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-showBytesOnGraph.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-wordSize.html src/main/resources/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration/config.jelly src/main/resources/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration/help-graphCaption.html src/main/resources/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration/help-graphDataList.html src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/config.jelly src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/help-configurationFile.html src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/help-mapFile.html src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/help-parserUniqueName.html src/main/resources/net/praqma/jenkins/memorymap/parser/GccMemoryMapParser/config.jelly 

[JIRA] [buildresult-trigger-plugin] (JENKINS-31178) BuildResultTrigger+Plugin is not triggering the job

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31178 
 
 
 
  BuildResultTrigger+Plugin is not triggering the job   
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [buildresult-trigger-plugin] (JENKINS-31178) BuildResultTrigger+Plugin is not triggering the job

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-31178 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: BuildResultTrigger+Plugin is not triggering the job   
 
 
 
 
 
 
 
 
 
 
Fixed the component 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [buildresult-trigger-plugin] (JENKINS-31178) BuildResultTrigger+Plugin is not triggering the job

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31178 
 
 
 
  BuildResultTrigger+Plugin is not triggering the job   
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

Component/s:
 
 buildresult-trigger-plugin 
 
 
 

Component/s:
 
 _test 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [buildresult-trigger-plugin] (JENKINS-31178) BuildResultTrigger+Plugin is not triggering the job

[riyas.mohiyudhee...@aas.com.au (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Riyas Mohiyudheen commented on  JENKINS-31178 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: BuildResultTrigger+Plugin is not triggering the job   
 
 
 
 
 
 
 
 
 
 
HI Oleg Nenashev, 
Please let me know what should we do configure from our end after fix. 
Regards, Riyas 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [extensible-choice-parameter-plugin] (JENKINS-17875) Make Jenkins environment variables available to dynamic providers

[jerrys...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jerryshea commented on  JENKINS-17875 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make Jenkins environment variables available to dynamic providers  
 
 
 
 
 
 
 
 
 
 
Hi, I appreciate that this issue is closed but can you advise how do I actually use an environment variable in a groovy script? Neither of the below work for me: 

 

"${BUILD_NUMBER}"
System.env["BUILD_NUMBER"]
 

 
Thanks! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [slack-plugin] (JENKINS-30559) Option to omit commit messages from a notification message

[sam.mxra...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Gleske commented on  JENKINS-30559 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Option to omit commit messages from a notification message  
 
 
 
 
 
 
 
 
 
 
Merged and possibly fixed in the 2.0 release. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [email-ext-plugin] (JENKINS-30854) Support AWS SES Message IDs for In-Reply-To header

[devnull.jenk...@molb.org (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Johannes Weißl commented on  JENKINS-30854 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support AWS SES Message IDs for In-Reply-To header  
 
 
 
 
 
 
 
 
 
 
Thanks a lot! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [_test] (JENKINS-31178) BuildResultTrigger+Plugin is not triggering the job

[riyas.mohiyudhee...@aas.com.au (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Riyas Mohiyudheen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31178 
 
 
 
  BuildResultTrigger+Plugin is not triggering the job   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 

Components:
 

 _test 
 
 
 

Created:
 

 27/Oct/15 6:30 AM 
 
 
 

Environment:
 

 All Tets 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Riyas Mohiyudheen 
 
 
 
 
 
 
 
 
 
 
BuildResultTrigger+Plugin has been configured for Success of a another job but it is not triggered at all. Please help as this is a blocker for now 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 

[JIRA] [buildresult-trigger-plugin] (JENKINS-31178) BuildResultTrigger+Plugin is not triggering the job

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-31178 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: BuildResultTrigger+Plugin is not triggering the job   
 
 
 
 
 
 
 
 
 
 
No idea. I have not ever used this plugin.  BTW I would recommend to take a look on this guide and to provide more details: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue .Build logs and other such information would be useful 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [other] (JENKINS-30958) Slaves using 10 executor whereas specified 4

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30958 
 
 
 
  Slaves using 10 executor whereas specified 4  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [other] (JENKINS-30958) Slaves using 10 executor whereas specified 4

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-30958 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Slaves using 10 executor whereas specified 4  
 
 
 
 
 
 
 
 
 
 
Hi Pranav, please clarify the question. 
 

Which type of jobs do you run?
 

Which Jenkins core and plugin versions do you use
 
 
>Also, it happens with some of the machine while some of the machine have only 4 jobs whereas based on my understanding those jobs should be equally distributed to all slaves 
It's not correct. By default Jenkins schedules builds to nodes having workspaces. BTW there are plugins allowing to alter the behavior 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-31174) Exceptions during script evaluation not logged

[m...@daniel-spilker.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Spilker commented on  JENKINS-31174 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Exceptions during script evaluation not logged  
 
 
 
 
 
 
 
 
 
 
Let's take an example which isn't completely broken: 

 

job('example') {
  foo()
}
 

 
It will produce: 

 

Processing provided DSL script
ERROR: (script, line 2) No signature of method: javaposse.jobdsl.dsl.jobs.FreeStyleJob.foo() is applicable for argument types: () values: []
Possible solutions: find(), any(), jdk(java.lang.String), scm(groovy.lang.Closure), any(groovy.lang.Closure), find(groovy.lang.Closure)
Finished: FAILURE
 

 
What's wrong with that? It identifies the problem, notes the correct line and even tries to give a solution. 
Your pull request will hide a message with a stack trace in the Jenkins system log. How does that improve the situation? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [github-plugin] (JENKINS-27154) Make the github-plugin commit status configurable instead of tied to the project name

[lan...@yandex.ru (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kirill Merkushev assigned an issue to Kirill Merkushev 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27154 
 
 
 
  Make the github-plugin commit status configurable instead of tied to the project name  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kirill Merkushev 
 
 
 

Assignee:
 
 Kirill Merkushev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gitlab-hook-plugin] (JENKINS-31179) Gitlab web hook is not working.

[linh....@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 linh nguyen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31179 
 
 
 
  Gitlab web hook is not working.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 gitlab-hook-plugin 
 
 
 

Created:
 

 27/Oct/15 8:47 AM 
 
 
 

Environment:
 

 Jenkins version: 1.573  Gitlab hook plugin: 1.3.1  GIT plugin: 2.3.5  GIT client plugin: 1.9.0  
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 linh nguyen 
 
 
 
 
 
 
 
 
 
 
Previous, I added a web hooks http://jenkins.my.domain/gitlab/build_now in my project on gitlab site, then I access to Settings > Web hooks > and press Test hook button. My Jenkins server run build my app.  However, a week ago ( on monday, Oct 19, 2015), my Jenkins could not auto build when having a new commit to gitlab. And, I tried to test it by pressing Test hook button on gitlab site, It spent a very long time and returned a error 500  Then I checked log in production.log and got:  Completed 500 Internal Server Error in 10158ms 
_{{Timeout::Error (execution expired): app/models/web_hook.rb:31:in `execute' app/services/test_hook_service.rb:4:in `execute' app/controllers/projects/hooks_controller.rb:27:in `test' app/controllers/application_controller.rb:57:in `set_current_user_for_thread'}}_ 
I have been google and find that https://gitlab.com/gitlab-org/gitlab-ce/issues/520 and he said that edit 

[JIRA] [memory-map-plugin] (JENKINS-29804) Parse error on comments in linker file (GCC) (Praqma case 13367)

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29804 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Parse error on comments in linker file (GCC) (Praqma case 13367)  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Mads Nielsen Path: src/main/java/net/praqma/jenkins/memorymap/parser/gcc/GccMemoryMapParser.java src/test/java/net/praqma/jenkins/unit/HexUtilsTest.java src/test/java/net/praqma/jenkins/unit/MemoryMapGccParserTest.java http://jenkins-ci.org/commit/memory-map-plugin/1647bd4daece1a993cd0d8d2e01a29b369f87e33 Log: JENKINS-29804 Add clearer error message when invalid memory length is parsed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [memory-map-plugin] (JENKINS-19841) Add GCC Parser support ( praqma case 10103 )

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-19841 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add GCC Parser support ( praqma case 10103 )  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: thi Path: README.md check_for_changelog.rb pom.xml src/main/java/net/praqma/jenkins/memorymap/MemoryMapBuildAction.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapProjectAction.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapRecorder.java src/main/java/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration.java src/main/java/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfigurationDescriptor.java src/main/java/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/GccMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/KeilMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapConfigFileParserDelegate.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapMapParserDelegate.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapParsable.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapParserDescriptor.java src/main/java/net/praqma/jenkins/memorymap/parser/TexasInstrumentsMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/gcc/GccMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/gcc/ParserItemMixin.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapConfigMemory.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapConfigMemoryItem.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapGroup.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapParsingResult.java src/main/java/net/praqma/jenkins/memorymap/util/FileFoundable.java src/main/java/net/praqma/jenkins/memorymap/util/HexUtils.java src/main/java/net/praqma/jenkins/memorymap/util/MemoryMapError.java src/main/java/net/praqma/jenkins/memorymap/util/MemoryMapFileNotFoundError.java src/main/java/net/praqma/jenkins/memorymap/util/MemoryMapMemorySelectionError.java src/main/resources/net/praqma/jenkins/memorymap/MemoryMapProjectAction/floatingBox.jelly src/main/resources/net/praqma/jenkins/memorymap/MemoryMapProjectAction/index.jelly src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/config.jelly src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-chosenParser.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-graphConfiguration.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-scale.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-showBytesOnGraph.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-wordSize.html src/main/resources/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration/config.jelly src/main/resources/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration/help-graphCaption.html src/main/resources/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration/help-graphDataList.html src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/config.jelly src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/help-configurationFile.html src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/help-mapFile.html src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/help-parserUniqueName.html src/main/resources/net/praqma/jenkins/memorymap/parser/GccMemoryMapParser/config.jelly src/main/resources/net/praqma/jenkins/memorymap/parser/KeilMemoryMapParser/config.jelly src/main/resources/net/praqma/jenkins/memorymap/parser/TexasInstrumentsMemoryMapParser/config.jelly src/main/resources/net/praqma/jenkins/memorymap/parser/gcc/GccMemoryMapParser/config.jelly src/main/resources/net/praqma/jenkins/ti/28069_RAM_lnk.cmd 

[JIRA] [memory-map-plugin] (JENKINS-19841) Add GCC Parser support ( praqma case 10103 )

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-19841 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add GCC Parser support ( praqma case 10103 )  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Thierry Lacour Path: .gitignore README.md check_for_changelog.rb pom.xml src/main/java/net/praqma/jenkins/memorymap/MemoryMapBuildAction.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapDslExtension.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapGraphDslContext.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapJobDslContext.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapParserDslContext.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapProjectAction.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapRecorder.java src/main/java/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration.java src/main/java/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfigurationDescriptor.java src/main/java/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/GccMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/KeilMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapConfigFileParserDelegate.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapMapParserDelegate.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapParsable.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapParserDescriptor.java src/main/java/net/praqma/jenkins/memorymap/parser/TexasInstrumentsMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/gcc/GccMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/ti/TexasInstrumentsMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapConfigMemory.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapConfigMemoryItem.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapGroup.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapParsingResult.java src/main/java/net/praqma/jenkins/memorymap/util/FileFoundable.java src/main/java/net/praqma/jenkins/memorymap/util/HexUtils.java src/main/java/net/praqma/jenkins/memorymap/util/MemoryMapError.java src/main/java/net/praqma/jenkins/memorymap/util/MemoryMapFileNotFoundError.java src/main/java/net/praqma/jenkins/memorymap/util/MemoryMapMemorySelectionError.java src/main/resources/net/praqma/jenkins/memorymap/MemoryMapProjectAction/floatingBox.jelly src/main/resources/net/praqma/jenkins/memorymap/MemoryMapProjectAction/index.jelly src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/config.jelly src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-chosenParser.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-graphConfiguration.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-scale.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-showBytesOnGraph.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-wordSize.html src/main/resources/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration/config.jelly src/main/resources/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration/help-graphCaption.html src/main/resources/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration/help-graphDataList.html src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/config.jelly src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/help-configurationFile.html src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/help-mapFile.html src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/help-parserUniqueName.html src/main/resources/net/praqma/jenkins/memorymap/parser/GccMemoryMapParser/config.jelly 

[JIRA] [memory-map-plugin] (JENKINS-29052) Plugin fails when defining a graphless parser (our case 13212)

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29052 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Plugin fails when defining a graphless parser (our case 13212)  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Thierry Lacour Path: .gitignore README.md check_for_changelog.rb pom.xml src/main/java/net/praqma/jenkins/memorymap/MemoryMapBuildAction.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapDslExtension.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapGraphDslContext.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapJobDslContext.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapParserDslContext.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapProjectAction.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapRecorder.java src/main/java/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration.java src/main/java/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfigurationDescriptor.java src/main/java/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/GccMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/KeilMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapConfigFileParserDelegate.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapMapParserDelegate.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapParsable.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapParserDescriptor.java src/main/java/net/praqma/jenkins/memorymap/parser/TexasInstrumentsMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/gcc/GccMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/ti/TexasInstrumentsMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapConfigMemory.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapConfigMemoryItem.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapGroup.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapParsingResult.java src/main/java/net/praqma/jenkins/memorymap/util/FileFoundable.java src/main/java/net/praqma/jenkins/memorymap/util/HexUtils.java src/main/java/net/praqma/jenkins/memorymap/util/MemoryMapError.java src/main/java/net/praqma/jenkins/memorymap/util/MemoryMapFileNotFoundError.java src/main/java/net/praqma/jenkins/memorymap/util/MemoryMapMemorySelectionError.java src/main/resources/net/praqma/jenkins/memorymap/MemoryMapProjectAction/floatingBox.jelly src/main/resources/net/praqma/jenkins/memorymap/MemoryMapProjectAction/index.jelly src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/config.jelly src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-chosenParser.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-graphConfiguration.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-scale.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-showBytesOnGraph.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-wordSize.html src/main/resources/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration/config.jelly src/main/resources/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration/help-graphCaption.html src/main/resources/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration/help-graphDataList.html src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/config.jelly src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/help-configurationFile.html src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/help-mapFile.html src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/help-parserUniqueName.html src/main/resources/net/praqma/jenkins/memorymap/parser/GccMemoryMapParser/config.jelly 

[JIRA] [memory-map-plugin] (JENKINS-31021) (Praqma case 13731) HexUtils should return hex strings with consistent formatting

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31021 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: (Praqma case 13731) HexUtils should return hex strings with consistent formatting  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Thierry Lacour Path: pom.xml src/main/java/net/praqma/jenkins/memorymap/MemoryMapBuildAction.java src/main/java/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/util/HexUtils.java src/test/java/net/praqma/jenkins/integration/TestUtils.java src/test/java/net/praqma/jenkins/unit/HexUtilsTest.java src/test/java/net/praqma/jenkins/unit/MemoryMapGccParserTest.java http://jenkins-ci.org/commit/memory-map-plugin/32fa80fe3aa44c7cec6f413c0011c7feb66e7bf7 Log: Merge branch 'JENKINS-31021' into useCaseTests 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [memory-map-plugin] (JENKINS-31021) (Praqma case 13731) HexUtils should return hex strings with consistent formatting

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31021 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: (Praqma case 13731) HexUtils should return hex strings with consistent formatting  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Thierry Lacour Path: src/main/java/net/praqma/jenkins/memorymap/util/HexUtils.java src/test/java/net/praqma/jenkins/unit/HexUtilsTest.java http://jenkins-ci.org/commit/memory-map-plugin/f761baddd4af3f62a6f83c95b3fcdefa083bde06 Log: JENKINS-31021 HexifiableString should have consistent String formatting. 
Added toFormattedHexString to HexifiableString 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [memory-map-plugin] (JENKINS-29052) Plugin fails when defining a graphless parser (our case 13212)

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29052 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Plugin fails when defining a graphless parser (our case 13212)  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Thierry Lacour Path: src/test/java/net/praqma/jenkins/integration/GraphlessPublisherFailsIT.java src/test/java/net/praqma/jenkins/integration/JENKINS_29052_IT.java http://jenkins-ci.org/commit/memory-map-plugin/b0dca849727d61d5dc87d25d50a1dbdaec70ef9f Log: Renamed test to reference its case, JENKINS-29052 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [memory-map-plugin] (JENKINS-30000) Refactor Texas Instruments Parser (Part one) (Praqma case 13215)

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-3 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Refactor Texas Instruments Parser (Part one) (Praqma case 13215)   
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Thierry Lacour Path: src/main/java/net/praqma/jenkins/memorymap/MemoryMapRecorder.java src/main/java/net/praqma/jenkins/memorymap/parser/TexasInstrumentsMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/ti/TexasInstrumentsMemoryMapParser.java http://jenkins-ci.org/commit/memory-map-plugin/c5f48d09479bf4041932bbe5120af0de061badd8 Log: JENKINS-3 (Refactor TI parser) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [memory-map-plugin] (JENKINS-29804) Parse error on comments in linker file (GCC) (Praqma case 13367)

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29804 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Parse error on comments in linker file (GCC) (Praqma case 13367)  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Thierry Lacour Path: .gitignore README.md check_for_changelog.rb pom.xml src/main/java/net/praqma/jenkins/memorymap/MemoryMapBuildAction.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapDslExtension.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapGraphDslContext.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapJobDslContext.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapParserDslContext.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapProjectAction.java src/main/java/net/praqma/jenkins/memorymap/MemoryMapRecorder.java src/main/java/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration.java src/main/java/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfigurationDescriptor.java src/main/java/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/GccMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/KeilMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapConfigFileParserDelegate.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapMapParserDelegate.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapParsable.java src/main/java/net/praqma/jenkins/memorymap/parser/MemoryMapParserDescriptor.java src/main/java/net/praqma/jenkins/memorymap/parser/TexasInstrumentsMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/gcc/GccMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/parser/ti/TexasInstrumentsMemoryMapParser.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapConfigMemory.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapConfigMemoryItem.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapGroup.java src/main/java/net/praqma/jenkins/memorymap/result/MemoryMapParsingResult.java src/main/java/net/praqma/jenkins/memorymap/util/FileFoundable.java src/main/java/net/praqma/jenkins/memorymap/util/HexUtils.java src/main/java/net/praqma/jenkins/memorymap/util/MemoryMapError.java src/main/java/net/praqma/jenkins/memorymap/util/MemoryMapFileNotFoundError.java src/main/java/net/praqma/jenkins/memorymap/util/MemoryMapMemorySelectionError.java src/main/resources/net/praqma/jenkins/memorymap/MemoryMapProjectAction/floatingBox.jelly src/main/resources/net/praqma/jenkins/memorymap/MemoryMapProjectAction/index.jelly src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/config.jelly src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-chosenParser.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-graphConfiguration.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-scale.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-showBytesOnGraph.html src/main/resources/net/praqma/jenkins/memorymap/MemoryMapRecorder/help-wordSize.html src/main/resources/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration/config.jelly src/main/resources/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration/help-graphCaption.html src/main/resources/net/praqma/jenkins/memorymap/graph/MemoryMapGraphConfiguration/help-graphDataList.html src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/config.jelly src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/help-configurationFile.html src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/help-mapFile.html src/main/resources/net/praqma/jenkins/memorymap/parser/AbstractMemoryMapParser/help-parserUniqueName.html src/main/resources/net/praqma/jenkins/memorymap/parser/GccMemoryMapParser/config.jelly 

[JIRA] [core] (JENKINS-31181) setting slave temporally offline/online not persisted to disk

[asmu...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Asmund Ostvold created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31181 
 
 
 
  setting slave temporally offline/online not persisted to disk  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi 
 
 
 

Components:
 

 core, ssh-slaves-plugin 
 
 
 

Created:
 

 27/Oct/15 9:36 AM 
 
 
 

Environment:
 

 Jenkins ver. 1.625.1 and Jenkins ver. 1.634 
 
 
 

Labels:
 

 slave jenkins 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Asmund Ostvold 
 
 
 
 
 
 
 
 
 
 
Setting a node temporarily to offline or online is not persisted to disk. Normally this is not an issue but each time I have to restart Jenkins this a big issue. Nodes that should be offiline after a restart is not and nodes that should be online is offiline. The only way to update the temporarily offline status is to change something in the node configuration and save.  
I believed this worked in the past I do not know the version. I do not restart often and it took me some time to notice this.  
 
 
 
 
 

[JIRA] [extensible-choice-parameter-plugin] (JENKINS-17875) Make Jenkins environment variables available to dynamic providers

[jerrys...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jerryshea commented on  JENKINS-17875 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make Jenkins environment variables available to dynamic providers  
 
 
 
 
 
 
 
 
 
 
Ah... thanks. Should the above syntax work to get other environment variables such as jenkins global environment variables?  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-31133) Allow processing the plugin jar file before generating the hpi file

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31133 
 
 
 
  Allow processing the plugin jar file before generating the hpi file  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-31133) Allow processing the plugin jar file before generating the hpi file

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31133 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow processing the plugin jar file before generating the hpi file  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Stephen Connolly Path: src/it/process-jar/verify.groovy http://jenkins-ci.org/commit/maven-hpi-plugin/90039948f06623f0ef03829a8848cf47e93576ec Log: 

JENKINS-31133
 Really verify the content of the jar 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-31133) Allow processing the plugin jar file before generating the hpi file

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31133 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow processing the plugin jar file before generating the hpi file  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Stephen Connolly Path: src/it/process-jar/invoker.properties src/it/process-jar/pom.xml src/it/process-jar/src/keystore/testing.jks src/it/process-jar/src/main/java/org/jenkinsci/tools/hpi/its/HelloWorldBuilder.java src/it/process-jar/src/main/resources/index.jelly src/it/process-jar/src/main/resources/org/jenkinsci/tools/hpi/its/HelloWorldBuilder/config.jelly src/it/process-jar/src/main/resources/org/jenkinsci/tools/hpi/its/HelloWorldBuilder/global.jelly src/it/process-jar/src/main/resources/org/jenkinsci/tools/hpi/its/HelloWorldBuilder/help-name.html src/it/process-jar/src/main/resources/org/jenkinsci/tools/hpi/its/Messages.properties src/it/process-jar/src/main/webapp/help-globalConfig.html src/it/process-jar/verify.groovy src/main/java/org/jenkinsci/maven/plugins/hpi/AbstractHpiMojo.java src/main/java/org/jenkinsci/maven/plugins/hpi/HpiMojo.java src/main/java/org/jenkinsci/maven/plugins/hpi/JarMojo.java http://jenkins-ci.org/commit/maven-hpi-plugin/761273ca14ec07c53b41aaf5b0f76be2783f3cf6 Log: [FIXED JENKINS-31133] Allow processing the plugin jar file before generating the hpi file 
 

The attached integration test verifies the jarsigner usecase (although manual verification was required as unzipping the .hpi to unzip the .jar to verify the signature present has been left as an excercise to the reader)
 

The shade usecase reveals that the maven-shade-plugin does not currently support the designed use-case... off to maven land it would seem... (though the required hooks are present in this plugin)
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received 

[JIRA] [core] (JENKINS-31133) Allow processing the plugin jar file before generating the hpi file

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31133 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow processing the plugin jar file before generating the hpi file  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Stephen Connolly Path: src/it/process-jar/invoker.properties src/it/process-jar/pom.xml src/it/process-jar/src/keystore/testing.jks src/it/process-jar/src/main/java/org/jenkinsci/tools/hpi/its/HelloWorldBuilder.java src/it/process-jar/src/main/resources/index.jelly src/it/process-jar/src/main/resources/org/jenkinsci/tools/hpi/its/HelloWorldBuilder/config.jelly src/it/process-jar/src/main/resources/org/jenkinsci/tools/hpi/its/HelloWorldBuilder/global.jelly src/it/process-jar/src/main/resources/org/jenkinsci/tools/hpi/its/HelloWorldBuilder/help-name.html src/it/process-jar/src/main/resources/org/jenkinsci/tools/hpi/its/Messages.properties src/it/process-jar/src/main/webapp/help-globalConfig.html src/it/process-jar/verify.groovy src/main/java/org/jenkinsci/maven/plugins/hpi/AbstractHpiMojo.java src/main/java/org/jenkinsci/maven/plugins/hpi/HpiMojo.java src/main/java/org/jenkinsci/maven/plugins/hpi/JarMojo.java http://jenkins-ci.org/commit/maven-hpi-plugin/850dd747ee5e863de80f4d85492870b63a54722a Log: Merge pull request #24 from stephenc/jenkins-31133 
[FIXED JENKINS-31133] Allow processing the plugin jar file before generating the hpi file 
Compare: https://github.com/jenkinsci/maven-hpi-plugin/compare/0249873f5b85...850dd747ee5e 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-31133) Allow processing the plugin jar file before generating the hpi file

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31133 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow processing the plugin jar file before generating the hpi file  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Stephen Connolly Path: src/it/process-jar/pom.xml http://jenkins-ci.org/commit/maven-hpi-plugin/08b8a7ff8ef2eaf442f11c5a76b80baf67cffdd7 Log: 

JENKINS-31133
 Confirmed: shade processes optional dependencies 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-31182) Jenkins: focus at the boom of the page (and large number of slave

[raphael.uni...@stef.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raphaël UNIQUE updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31182 
 
 
 
  Jenkins: focus at the boom of the page (and large number of slave  
 
 
 
 
 
 
 
 
 

Change By:
 
 Raphaël UNIQUE 
 
 
 

Attachment:
 
 screenshot-logon.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-31067) Subversion polling does not work when the Repository URL contains a variable

[rec...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31067 
 
 
 
  Subversion polling does not work when the Repository URL contains a variable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-31180) SVN checkout single file into Folder

[rec...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto closed an issue as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31180 
 
 
 
  SVN checkout single file into Folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-17616) Performance issue with Subversion plugin - trigger build on SVN commit takes too long

[rec...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-17616 
 
 
 
  Performance issue with Subversion plugin - trigger build on SVN commit takes too long  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Assignee:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [xunit-plugin] (JENKINS-31101) XUnit is not rendering the test result summary correctly for a Custom tool

[daniel.mendesdasi...@arhs-cube.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel MS commented on  JENKINS-31101 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: XUnit is not rendering the test result summary correctly for a Custom tool  
 
 
 
 
 
 
 
 
 
 
Hi Gregory Boissinot  Is this ticket correctly created ?  Is this a bug or misconfiguration ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5

[rec...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-27084 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SVN authentication fails using subversion plugin v.2.5  
 
 
 
 
 
 
 
 
 
 
Rasmus Pedersen, If you agree, I'm going to close this ticket. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [extensible-choice-parameter-plugin] (JENKINS-17875) Make Jenkins environment variables available to dynamic providers

[de...@ikedam.jp (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam commented on  JENKINS-17875 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make Jenkins environment variables available to dynamic providers  
 
 
 
 
 
 
 
 
 
 
Unfortunately, you never get BUILD_NUMBER as the script runs BEFORE builds start. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-31111) DownstreamTriggerParameterContext should be an ExtensibleContext

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-3 
 
 
 
  DownstreamTriggerParameterContext should be an ExtensibleContext  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-31111) DownstreamTriggerParameterContext should be an ExtensibleContext

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-3 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: DownstreamTriggerParameterContext should be an ExtensibleContext  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Spilker Path: docs/Extending-the-DSL.md docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/common/AbstractDownstreamTriggerContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/common/DownstreamTriggerParameterContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/BuildPipelineContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/DownstreamContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/DownstreamTriggerContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/DownstreamContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/DownstreamTriggerContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/MultiJobStepContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/PhaseContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/PhaseJobContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/StepContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/common/DownstreamTriggerParameterContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/cc268bd4a8e09a8f4f0449aa6aba043ac2ebe236 Log: made DownstreamTriggerParameterContext extensible 
[FIXES JENKINS-3] 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-31111) DownstreamTriggerParameterContext should be an ExtensibleContext

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-3 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: DownstreamTriggerParameterContext should be an ExtensibleContext  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Spilker Path: docs/Extending-the-DSL.md docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/common/AbstractDownstreamTriggerContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/common/DownstreamTriggerParameterContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/BuildPipelineContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/DownstreamContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/DownstreamTriggerContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/DownstreamContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/DownstreamTriggerContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/MultiJobStepContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/PhaseContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/PhaseJobContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/StepContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/common/DownstreamTriggerParameterContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/f8fcad9f91ee5f84a56cc7c4adb53b5b95446a50 Log: Merge pull request #647 from daspilker/

JENKINS-3
 


JENKINS-3
 made DownstreamTriggerParameterContext extensible 
Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/957da9704b0f...f8fcad9f91ee 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
 

[JIRA] [docker-custom-build-environment-plugin] (JENKINS-31166) 'ls' and 'mkdir' "not found" since v1.6.2

[vinc...@latombe.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vincent Latombe started work on  JENKINS-31166 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Vincent Latombe 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-31067) Subversion polling does not work when the Repository URL contains a variable

[rec...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-31067 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Subversion polling does not work when the Repository URL contains a variable  
 
 
 
 
 
 
 
 
 
 
chris_mh3, thanks so much for your feedback. I've added a comment in the PR. 
I hope to cut a release soon. Probably, this week. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [integrity-plugin] (JENKINS-25228) Using the integrity-plugin together with concurrent builds causes SQL Exceptions

[chahine.a...@invensity.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Leon Leon commented on  JENKINS-25228 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Using the integrity-plugin together with concurrent builds causes SQL Exceptions  
 
 
 
 
 
 
 
 
 
 
Yes, workflow jobs. We are already using the PTC Plugin special one off version 1.31-4.10.9049 with Workflow Plugin version 1.10 and 1.11 beta and we are "sometimes" facing the issue mentionaed earlier. Is it not unadvisable to use the PTC Plugin with Workflow ? Thank you for your help. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-31180) SVN checkout single file into Folder

[rec...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-31180 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SVN checkout single file into Folder  
 
 
 
 
 
 
 
 
 
 
Hariharan Ramkumar, I recommend you to send this kind of questions to jenkinsci-users mailing list (jenkinsci-us...@googlegroups.com). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [integrity-plugin] (JENKINS-25228) Using the integrity-plugin together with concurrent builds causes SQL Exceptions

[chahine.a...@invensity.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Leon Leon edited a comment on  JENKINS-25228 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Using the integrity-plugin together with concurrent builds causes SQL Exceptions  
 
 
 
 
 
 
 
 
 
 Yes, workflow jobs.We are already using the PTC Plugin  special one off version 1.31-4.10.9049 with Workflow Plugin version 1.10 and 1.11 beta and we are "sometimes" facing the issue  mentionaed  mentioned  earlier. Is it not unadvisable to use the PTC Plugin with Workflow ?Thank you for your help. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sauce-ondemand-plugin] (JENKINS-30065) SELENIUM_PLATFORM not always properly set when using Matrix Axis -> Sauce Labs WebDriver tests

[elga...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Leo Gallucci resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Works 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-30065 
 
 
 
  SELENIUM_PLATFORM not always properly set when using Matrix Axis -> Sauce Labs WebDriver tests  
 
 
 
 
 
 
 
 
 

Change By:
 
 Leo Gallucci 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [email-ext-plugin] (JENKINS-31177) email notification corrupted due to build failure "FATAL: java.io.IOException: Unexpected termination of the channel"

[slide.o....@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Earl commented on  JENKINS-31177 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: email notification corrupted due to build failure "FATAL: java.io.IOException: Unexpected termination of the channel"  
 
 
 
 
 
 
 
 
 
 
Looks like a remoting issue, not an issue with email-ext. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [docker-custom-build-environment-plugin] (JENKINS-31166) 'ls' and 'mkdir' "not found" since v1.6.2

[vinc...@latombe.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vincent Latombe assigned an issue to Vincent Latombe 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31166 
 
 
 
  'ls' and 'mkdir' "not found" since v1.6.2  
 
 
 
 
 
 
 
 
 

Change By:
 
 Vincent Latombe 
 
 
 

Assignee:
 
 Nicolas De Loof Vincent Latombe 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-31182) Jenkins: focus at the boom of the page (and large number of slave

[raphael.uni...@stef.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raphaël UNIQUE created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31182 
 
 
 
  Jenkins: focus at the boom of the page (and large number of slave  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 27/Oct/15 10:08 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Raphaël UNIQUE 
 
 
 
 
 
 
 
 
 
 
Hello, We have a large number of slave (80). So when a user have to log on, he can't see the user/password field because the focus is at the end of the page. 
should the focus be of the user/password fields during log on? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 

[JIRA] [core] (JENKINS-31182) Jenkins: focus at the boom of the page (and large number of slave)

[raphael.uni...@stef.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raphaël UNIQUE updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31182 
 
 
 
  Jenkins: focus at the boom of the page (and large number of slave)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Raphaël UNIQUE 
 
 
 

Summary:
 
 Jenkins: focus at the boom of the page (and large number of slave ) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-31180) SVN checkout single file into Folder

[rec...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31180 
 
 
 
  SVN checkout single file into Folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-31180) SVN checkout single file into Folder

[hari...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hariharan Ramkumar created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31180 
 
 
 
  SVN checkout single file into Folder  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi 
 
 
 

Attachments:
 

 Console Output.txt, SVN checkout file.PNG 
 
 
 

Components:
 

 subversion-plugin, svnmerge-plugin 
 
 
 

Created:
 

 27/Oct/15 9:06 AM 
 
 
 

Environment:
 

 Jenkins ver. 1.609.1.1 (CloudBees Jenkins Enterprise 15.05),  JDK 1.7, Browser : All browsers. 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Hariharan Ramkumar 
 
 
 
 
 
 
 
 
 
 
I would like to checkout the only one file form SVN Folder. This folder has number of files but i am interested in only checkout one file. When i configure the SVN modules repository to point out to the only one file getting an error.  
Is there any way to configure in jenkins to checkout only one file into local folder for Job execution. \ 
Attached console error and current job configuration (with all files checkout from folder) 
 
 
   

[JIRA] [core] (JENKINS-31015) Failure when downloading zipped artifacts

[tonka3...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 tonka tonka commented on  JENKINS-31015 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failure when downloading zipped artifacts  
 
 
 
 
 
 
 
 
 
 
I have the same issue (Win 2008 R2 x64)  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-31067) Subversion polling does not work when the Repository URL contains a variable

[chris_...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 chris_mh3 commented on  JENKINS-31067 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Subversion polling does not work when the Repository URL contains a variable  
 
 
 
 
 
 
 
 
 
 
Looks good for me. Tested on our buildserver and my local jenkins (1.634) - works without the Environment Injector Plugin again. 
Thanks for the fix! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gitlab-hook-plugin] (JENKINS-31179) Gitlab web hook is not working.

[linh....@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 linh nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31179 
 
 
 
  Gitlab web hook is not working.  
 
 
 
 
 
 
 
 
 

Change By:
 
 linh nguyen 
 
 
 
 
 
 
 
 
 
 Previous, I added a web hooks http://jenkins.my.domain/gitlab/build_now in my project on gitlab site, then I access to Settings > Web hooks >   and press Test hook button. My Jenkins server run build my app. However, a week ago ( on monday, Oct 19, 2015), my Jenkins could not auto build when having a new commit to gitlab. And, I tried to test it by pressing Test hook button on gitlab site, It spent a very long time and returned a error 500 Then I checked log in production.log and got: Completed 500 Internal Server Error in 10158ms_{{Timeout::Error (execution expired):  app/models/web_hook.rb:31:in `execute'  app/services/test_hook_service.rb:4:in `execute'  app/controllers/projects/hooks_controller.rb:27:in `test'  app/controllers/application_controller.rb:57:in `set_current_user_for_thread'}}_I have been google and find that https://gitlab.com/gitlab-org/gitlab-ce/issues/520and he said that edit app/models/web_hook.rb file and change {{# HTTParty timeout  default_timeout 10}}to {{# HTTParty timeout  default_timeout 100}}Unfortunate, It bypass this error and display an other error: (502 Proxy error.) _The {quote}Proxy ErrorThe  proxy server received an invalid response from an upstream server.  \ The proxy server could not handle the request  POST  GET  / gitlab myproject / build_now hooks/207/test.   Reason: Error reading from remote server {quote}  _ I continuos google with error and find out the link https://groups.google.com/forum/#!topic/gitlabhq/Ji0ub1iQw-oThen i tried to edit by add this line to app/models/web_hook.rb{{WebHook.http_proxy('127.0.0.1', 8080)}}Then, I got the error:ActionController::RoutingError (No route matches [POST] "/gitlab/build_now"):  vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.3/lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'  vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.3/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'  vendor/bundle/ruby/1.9.1/gems/railties-4.0.3/lib/rails/rack/logger.rb:38:in `call_app'  vendor/bundle/ruby/1.9.1/gems/railties-4.0.3/lib/rails/rack/logger.rb:20:in `block in call'  vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.3/lib/active_support/tagged_logging.rb:67:in `block in tagged'  vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.3/lib/active_support/tagged_logging.rb:25:in `tagged'  vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.3/lib/active_support/tagged_logging.rb:67:in `tagged'  vendor/bundle/ruby/1.9.1/gems/railties-4.0.3/lib/rails/rack/logger.rb:20:in `call'  vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.3/lib/action_dispatch/middleware/request_id.rb:21:in `call'  vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in `call'  vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/runtime.rb:17:in `call'  vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/lock.rb:17:in `call'  vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in `call'  vendor/bundle/ruby/1.9.1/gems/railties-4.0.3/lib/rails/engine.rb:511:in `call'  vendor/bundle/ruby/1.9.1/gems/railties-4.0.3/lib/rails/application.rb:97:in `call'  vendor/bundle/ruby/1.9.1/gems/railties-4.0.3/lib/rails/railtie/configurable.rb:30:in `method_missing'  

[JIRA] [subversion-plugin] (JENKINS-30196) SVN Exception : svn: E210004: Malformed network data

[rec...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30196 
 
 
 
  SVN Exception : svn: E210004: Malformed network data  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Assignee:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-30196) SVN Exception : svn: E210004: Malformed network data

[rec...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30196 
 
 
 
  SVN Exception : svn: E210004: Malformed network data  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Labels:
 
 plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-17616) Performance issue with Subversion plugin - trigger build on SVN commit takes too long

[rec...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-17616 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Performance issue with Subversion plugin - trigger build on SVN commit takes too long  
 
 
 
 
 
 
 
 
 
 
Luis Roberto Perez Rios, Could you provide a step by step process to reproduce the problem? I'd like to help here. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-31067) Subversion polling does not work when the Repository URL contains a variable

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31067 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Subversion polling does not work when the Repository URL contains a variable  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: src/main/java/hudson/scm/SubversionSCM.java src/test/java/hudson/scm/SubversionEnvVarsTest.java http://jenkins-ci.org/commit/subversion-plugin/d5d3bb9b850190c3ad9968d403540d34efa94216 Log: Merge pull request #139 from recena/JENKINS-31067 
JENKINS-31067 Global env vars are not available on SVN Polling 
Compare: https://github.com/jenkinsci/subversion-plugin/compare/5da9ddbcf8d7...d5d3bb9b8501 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-31067) Subversion polling does not work when the Repository URL contains a variable

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31067 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Subversion polling does not work when the Repository URL contains a variable  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: src/main/java/hudson/scm/SubversionSCM.java http://jenkins-ci.org/commit/subversion-plugin/bc590398fa23ef459aeb101de6fef6884ab24af0 Log: JENKINS-31067 Global environment variables are not available on Subversion Polling 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-31067) Subversion polling does not work when the Repository URL contains a variable

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31067 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Subversion polling does not work when the Repository URL contains a variable  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: src/test/java/hudson/scm/SubversionEnvVarsTest.java http://jenkins-ci.org/commit/subversion-plugin/05f1b867e0d3080b26bbf9135d9f23cd050ef85f Log: JENKINS-31067 Added a test 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-30196) SVN Exception : svn: E210004: Malformed network data

[rec...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-30196 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SVN Exception : svn: E210004: Malformed network data  
 
 
 
 
 
 
 
 
 
 
Amitej Priyadarshi, If I send a PR with a possible solution, Could you try it in your environment? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gradle-jpi-plugin] (JENKINS-31186) Java stubs are not always regenerated from Groovy source

[m...@daniel-spilker.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Spilker created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31186 
 
 
 
  Java stubs are not always regenerated from Groovy source  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Daniel Spilker 
 
 
 

Components:
 

 gradle-jpi-plugin 
 
 
 

Created:
 

 27/Oct/15 1:19 PM 
 
 
 

Environment:
 

 Gradle 2.3  gradle-jpi-plugin 0.12.2 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Daniel Spilker 
 
 
 
 
 
 
 
 
 
 
When running a build without the clean task, the build may fail when running the compileJava task because the stubs generated from Groovy sources have not been regenerated by the stapler task. 

 

:job-dsl-plugin:localizer UP-TO-DATE
:job-dsl-plugin:stapler UP-TO-DATE
:job-dsl-plugin:compileJava
Download http://repo.jenkins-ci.org/public/org/jenkinsci/plugins/managed-scripts/1.2.1/managed-scripts-1.2.1.jar
warning: [options] bootstrap class path not set in conjunction with -source 1.6
warning: No SupportedSourceVersion annotation found on org.kohsuke.wpc.ProcessorImpl, returning RELEASE_6.
/scratch/jenkins/workspace/plugins/job-dsl-plugin/job-dsl-plugin/build/generated-src/stubs/javaposse/jobdsl/plugin/InterruptibleJobManagement.java:10: error: InterruptibleJobManagement is not abstract and does not override abstract method requireMinimumPluginVersion(String,String,boolean) in JobManagement

[JIRA] [vsphere-cloud-plugin] (JENKINS-30858) Slave Agent does not Disconnect During Windows Shutdown Sequence

[m...@vizrt.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikal Henriksen commented on  JENKINS-30858 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Slave Agent does not Disconnect During Windows Shutdown Sequence  
 
 
 
 
 
 
 
 
 
 
This sounds like the issue I'm having. It looks to me like the windows service tries to reconnect very soon after being disconnected, and the vSphere plugin does nothing to disallow this, even though it is shutting down the vm. 
As a workaround, I've set the slave agent to launch from a scheduled task instead, as described in https://wiki.jenkins-ci.org/display/JENKINS/Launch+Java+Web+Start+slave+agent+via+Windows+Scheduler 
Other than that, I can see two potential solutions to this issue: 
 

Deny slave agent connections during shutdown
 

Implement JENKINS-21810, to let us revert instantly without graceful shutdown on disconnect
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [integrity-plugin] (JENKINS-25228) Using the integrity-plugin together with concurrent builds causes SQL Exceptions

[cletusdso...@hotmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cletus D'Souza commented on  JENKINS-25228 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Using the integrity-plugin together with concurrent builds causes SQL Exceptions  
 
 
 
 
 
 
 
 
 
 
Correct, it is not advisable to use the current version of PTC Integrity Plugin with Workflow. Until I release 1.36, you are going to continue to get the error about Table/View doesn't exist. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ruby-runtime-plugin] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass

[pkelb...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Phellipe Ribeiro edited a comment on  JENKINS-31019 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass  
 
 
 
 
 
 
 
 
 
 Happening with me on Jenkins 1.635{{  java.io.IOException: Failed to dynamically deploy this plugin at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1328) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1126) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:745)Caused by: java.io.IOException: Failed to install ruby-runtime plugin at hudson.PluginManager.dynamicLoad(PluginManager.java:487) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1324) ... 5 moreCaused by: java.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:441) at hudson.PluginManager.dynamicLoad(PluginManager.java:478) ... 6 moreCaused by: java.lang.ClassCircularityError: org/jruby/RubyClass at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at org.jenkinsci.bytecode.ClassWriter.loadClass(ClassWriter.java:97) at org.jenkinsci.bytecode.ClassWriter.getCommonSuperClass(ClassWriter.java:64) at org.kohsuke.asm5.ClassWriter.getMergedType(ClassWriter.java:1654) at org.kohsuke.asm5.Frame.merge(Frame.java:1426) at org.kohsuke.asm5.Frame.merge(Frame.java:1374) at org.kohsuke.asm5.MethodWriter.visitMaxs(MethodWriter.java:1475) at org.kohsuke.asm5.tree.MethodNode.accept(MethodNode.java:833) at org.kohsuke.asm5.commons.JSRInlinerAdapter.visitEnd(JSRInlinerAdapter.java:187) at org.jenkinsci.bytecode.Transformer$1$1.visitEnd(Transformer.java:107) at org.kohsuke.asm5.MethodVisitor.visitEnd(MethodVisitor.java:877) at org.kohsuke.asm5.ClassReader.readMethod(ClassReader.java:1021) at org.kohsuke.asm5.ClassReader.accept(ClassReader.java:693) at org.kohsuke.asm5.ClassReader.accept(ClassReader.java:506) at org.jenkinsci.bytecode.Transformer.transform(Transformer.java:113) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:800) at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1310) at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1366) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1079) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.jenkinsci.jruby.RubyClassConverter.(RubyClassConverter.java:12) at org.jenkinsci.jruby.JRubyXStream.register(JRubyXStream.java:25) at ruby.RubyRuntimePlugin.initRubyXStreams(RubyRuntimePlugin.java:44) at ruby.RubyRuntimePlugin.start(RubyRuntimePlugin.java:28) at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:449) at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:438) ... 7 more  }}I'd be glad to provide any more useful info if needed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
  

[JIRA] [core] (JENKINS-31035) Introduce a policy for API deprecation

[kajkand...@conficio.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kaj Kandler commented on  JENKINS-31035 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Introduce a policy for API deprecation  
 
 
 
 
 
 
 
 
 
 
May I suggest to tie the removal of API to the change of major versions. That way it clearly signals that such incompatibilities might happen, when upgrading major versions. It makes management so much easier, than having to check with every single LTS/or other release for potentially breaking API's/plugins. 
So any major version change can remove API deprecated for more than 2 years. This should translate into the components (jars/maven dependencies) as well. And it is a policy that plugins that provide API can follow as well. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-2111) removing a job does not remove the workspace

[db...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-2111 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: removing a job does not remove the workspace  
 
 
 
 
 
 
 
 
 
 

Or one could solve this another way: If the main Jenkins server were to iterate over all the jobs, it could build up a Map listing, for each slave, what workspaces that slave might be asked about. Each slave could then be instructed to remove all the workspaces not in that list. This would ensure that each slave only retains the workspaces that the Jenkins server might ask it about - workspaces belonging to deleted/renamed builds would be removed, and workspaces belonging to valid builds that were last built on a different slave (and hence if the Jenkins server needed to access the workspace, it'd ask that slave not this one) would also be removed.
 
I think it's possible to reference environment variables in the 'Custom Workspace' option, and if those are only defined during a build or occasionally change values, this will result in the deletion of legitimate workspaces. 
Jenkins is a complex system, so any magic here will break things horribly for quite a few users – see the frequent complaints about the existing WorkspceCleanupThread. 
What would likely be feasible: If there are workspaces, ask whether they should be deleted as well when the project gets deleted. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [docker-build-publish-plugin] (JENKINS-29085) Allow to use the docker build --file option when building an image

[quentin.ner...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Quentin Nerden commented on  JENKINS-29085 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow to use the docker build --file option when building an image  
 
 
 
 
 
 
 
 
 
 
Looking at the screenshot under "How to use" in the jenkins wiki: https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Build+and+Publish+plugin shows a textbox called Build Context. This seems to be this feature. Was it part of the plugin and then removed? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-pipeline-plugin] (JENKINS-23532) Manual trigger execution causes TriggerException

[dsero...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Serodio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-23532 
 
 
 
  Manual trigger execution causes TriggerException  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Serodio 
 
 
 

Component/s:
 
 build-pipeline-plugin 
 
 
 

Component/s:
 
 delivery-pipeline-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-pipeline-plugin] (JENKINS-23532) Manual trigger execution causes TriggerException

[dsero...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Serodio commented on  JENKINS-23532 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Manual trigger execution causes TriggerException  
 
 
 
 
 
 
 
 
 
 
I'm seeing the same problem and I don't use Delivery Pipeline plugin. Also, the "No upstream trigger found for this projectMyProject" message is raised by Build Pipeline Plugin, so I think this bug is in Build Pipeline Plugin. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-2111) removing a job does not remove the workspace

[db...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck edited a comment on  JENKINS-2111 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: removing a job does not remove the workspace  
 
 
 
 
 
 
 
 
 
 {quote}Or one could solve this another way:If the main Jenkins server were to iterate over all the jobs, it could build up a Map listing, for each slave, what workspaces that slave might be asked about.Each slave could then be instructed to remove all the workspaces not in that list.This would ensure that each slave only retains the workspaces that the Jenkins server might ask it about - workspaces belonging to deleted/renamed builds would be removed, and workspaces belonging to valid builds that were last built on a different slave (and hence if the Jenkins server needed to access the workspace, it'd ask that slave not this one) would also be removed.{quote}I think it's possible to reference environment variables in the 'Custom Workspace' option, and if those are only defined during a build or occasionally change values, this will result in the deletion of legitimate workspaces.Jenkins is a complex system, so any magic here will break things horribly for quite a few users -- see the frequent complaints about the existing WorkspceCleanupThread.What would likely be feasible: If there are workspaces, ask whether they should be deleted as well when the project gets deleted.  If a slave is offline, it's your responsibility to clean up. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ruby-runtime-plugin] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass

[pkelb...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Phellipe Ribeiro commented on  JENKINS-31019 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass  
 
 
 
 
 
 
 
 
 
 
Happening with me on Jenkins 1.635 
{{java.io.IOException: Failed to dynamically deploy this plugin at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1328) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1126) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: Failed to install ruby-runtime plugin at hudson.PluginManager.dynamicLoad(PluginManager.java:487) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1324) ... 5 more Caused by: java.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:441) at hudson.PluginManager.dynamicLoad(PluginManager.java:478) ... 6 more Caused by: java.lang.ClassCircularityError: org/jruby/RubyClass at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at org.jenkinsci.bytecode.ClassWriter.loadClass(ClassWriter.java:97) at org.jenkinsci.bytecode.ClassWriter.getCommonSuperClass(ClassWriter.java:64) at org.kohsuke.asm5.ClassWriter.getMergedType(ClassWriter.java:1654) at org.kohsuke.asm5.Frame.merge(Frame.java:1426) at org.kohsuke.asm5.Frame.merge(Frame.java:1374) at org.kohsuke.asm5.MethodWriter.visitMaxs(MethodWriter.java:1475) at org.kohsuke.asm5.tree.MethodNode.accept(MethodNode.java:833) at org.kohsuke.asm5.commons.JSRInlinerAdapter.visitEnd(JSRInlinerAdapter.java:187) at org.jenkinsci.bytecode.Transformer$1$1.visitEnd(Transformer.java:107) at org.kohsuke.asm5.MethodVisitor.visitEnd(MethodVisitor.java:877) at org.kohsuke.asm5.ClassReader.readMethod(ClassReader.java:1021) at org.kohsuke.asm5.ClassReader.accept(ClassReader.java:693) at org.kohsuke.asm5.ClassReader.accept(ClassReader.java:506) at org.jenkinsci.bytecode.Transformer.transform(Transformer.java:113) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:800) at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1310) at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1366) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1079) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.jenkinsci.jruby.RubyClassConverter.(RubyClassConverter.java:12) at org.jenkinsci.jruby.JRubyXStream.register(JRubyXStream.java:25) at ruby.RubyRuntimePlugin.initRubyXStreams(RubyRuntimePlugin.java:44) at ruby.RubyRuntimePlugin.start(RubyRuntimePlugin.java:28) at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:449) at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:438) ... 7 more}} 
I'd be glad to provide any more useful info if needed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
   

[JIRA] [ruby-runtime-plugin] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass

[pkelb...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Phellipe Ribeiro edited a comment on  JENKINS-31019 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass  
 
 
 
 
 
 
 
 
 
 Happening with me on Jenkins 1.635 {{java.io.IOException :  Failed to dynamically deploy this plugin at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java  http : 1328) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1126) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:745)Caused by: java.io.IOException: Failed to install ruby-runtime plugin at hudson.PluginManager.dynamicLoad(PluginManager.java:487) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1324) ... 5 moreCaused by: java.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:441) at hudson.PluginManager.dynamicLoad(PluginManager.java:478) ... 6 moreCaused by: java.lang.ClassCircularityError: org / jruby / RubyClass at java goo . lang.Class.forName0(Native Method) gl/Ba1Hwn   at java.lang.Class.forName(Class.java:348)   at org.jenkinsci.bytecode.ClassWriter.loadClass(ClassWriter.java:97) at org.jenkinsci.bytecode.ClassWriter.getCommonSuperClass(ClassWriter.java:64) at org.kohsuke.asm5.ClassWriter.getMergedType(ClassWriter.java:1654) at org.kohsuke.asm5.Frame.merge(Frame.java:1426) at org.kohsuke.asm5.Frame.merge(Frame.java:1374) at org.kohsuke.asm5.MethodWriter.visitMaxs(MethodWriter.java:1475) at org.kohsuke.asm5.tree.MethodNode.accept(MethodNode.java:833) at org.kohsuke.asm5.commons.JSRInlinerAdapter.visitEnd(JSRInlinerAdapter.java:187) at org.jenkinsci.bytecode.Transformer$1$1.visitEnd(Transformer.java:107) at org.kohsuke.asm5.MethodVisitor.visitEnd(MethodVisitor.java:877) at org.kohsuke.asm5.ClassReader.readMethod(ClassReader.java:1021) at org.kohsuke.asm5.ClassReader.accept(ClassReader.java:693) at org.kohsuke.asm5.ClassReader.accept(ClassReader.java:506) at org.jenkinsci.bytecode.Transformer.transform(Transformer.java:113) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:800) at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1310) at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1366) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1079) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.jenkinsci.jruby.RubyClassConverter.(RubyClassConverter.java:12) at org.jenkinsci.jruby.JRubyXStream.register(JRubyXStream.java:25) at ruby.RubyRuntimePlugin.initRubyXStreams(RubyRuntimePlugin.java:44) at ruby.RubyRuntimePlugin.start(RubyRuntimePlugin.java:28) at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:449) at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:438) ... 7 more}} I'd be glad to provide any more useful info if needed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 

[JIRA] [docker-custom-build-environment-plugin] (JENKINS-31166) 'ls' and 'mkdir' "not found" since v1.6.2

[vinc...@latombe.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vincent Latombe closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31166 
 
 
 
  'ls' and 'mkdir' "not found" since v1.6.2  
 
 
 
 
 
 
 
 
 

Change By:
 
 Vincent Latombe 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [docker-custom-build-environment-plugin] (JENKINS-31166) 'ls' and 'mkdir' "not found" since v1.6.2

[vinc...@latombe.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vincent Latombe resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fixed in 1.6.3 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-31166 
 
 
 
  'ls' and 'mkdir' "not found" since v1.6.2  
 
 
 
 
 
 
 
 
 

Change By:
 
 Vincent Latombe 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [parameterized-trigger-plugin] (JENKINS-17460) Error occurs viewing build history on some builds

[bcov...@nycm.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-17460 
 
 
 
  Error occurs viewing build history on some builds  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [versionnumber-plugin] (JENKINS-30224) NPE thrown when a job uses an automatically installed JDK

[yoann.dubre...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Yoann Dubreuil commented on  JENKINS-30224 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: NPE thrown when a job uses an automatically installed JDK  
 
 
 
 
 
 
 
 
 
 
Thanks a lot! Release worked, I can find the plugin in Update Center 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [active-directory-plugin] (JENKINS-17718) Active Directory Plugin Fails

[bcov...@nycm.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny closed an issue as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-17718 
 
 
 
  Active Directory Plugin Fails  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sidebar-link-plugin] (JENKINS-18887) Alllow links to open in new window/tab

[bcov...@nycm.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny closed an issue as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-18887 
 
 
 
  Alllow links to open in new window/tab  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-2111) removing a job does not remove the workspace

[pjdar...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 pjdarton commented on  JENKINS-2111 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: removing a job does not remove the workspace  
 
 
 
 
 
 
 
 
 
 
I think that it would be very nice if, when a job does not have a custom workspace directory, renaming or deleting the job would rename or delete the workspace too (on ALL slaves). If a job has a custom workspace directory then things get more complicated, and that's where the "Don't delete the workspace if this job is deleted" check-box would be necessary. So, I'd suggest that this "Don't delete the workspace if this job is deleted" flag default to true where there is a custom workspace, and default to false (i.e. "do delete it") where a job just uses the workspace that Jenkins gives it. 
Or one could solve this another way: If the main Jenkins server were to iterate over all the jobs, it could build up a Map listing, for each slave, what workspaces that slave might be asked about. Each slave could then be instructed to remove all the workspaces not in that list. This would ensure that each slave only retains the workspaces that the Jenkins server might ask it about - workspaces belonging to deleted/renamed builds would be removed, and workspaces belonging to valid builds that were last built on a different slave (and hence if the Jenkins server needed to access the workspace, it'd ask that slave not this one) would also be removed. 
The link Distributed Workspace Clean plugin helps, but only works on valid builds - it doesn't remove data belonging to renamed/deleted builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-2111) removing a job does not remove the workspace

[pjdar...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 pjdarton edited a comment on  JENKINS-2111 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: removing a job does not remove the workspace  
 
 
 
 
 
 
 
 
 
 I think that it would be very nice if, when a job does not have a custom workspace directory, renaming or deleting the job would rename or delete the workspace too (on ALL slaves).If a job has a custom workspace directory then things get more complicated, and that's where the "Don't delete the workspace if this job is deleted" check-box would be necessary.So, I'd suggest that this "Don't delete the workspace if this job is deleted" flag default to true where there is a custom workspace, and default to false (i.e. "do delete it") where a job just uses the workspace that Jenkins gives it.Or one could solve this another way:If the main Jenkins server were to iterate over all the jobs, it could build up a Map listing, for each slave, what workspaces that slave might be asked about.Each slave could then be instructed to remove all the workspaces not in that list.This would ensure that each slave only retains the workspaces that the Jenkins server might ask it about - workspaces belonging to deleted/renamed builds would be removed, and workspaces belonging to valid builds that were last built on a different slave (and hence if the Jenkins server needed to access the workspace, it'd ask that slave not this one) would also be removed.The [ link  Distributed Workspace Clean plugin|https://wiki.jenkins-ci.org/display/JENKINS/Distributed+Workspace+Clean+plugin] helps, but only works on valid builds - it doesn't remove data belonging to renamed/deleted builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [scriptler-plugin] (JENKINS-29332) 404 on Scriptler repositories app

[aba...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 abayer commented on  JENKINS-29332 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: 404 on Scriptler repositories app  
 
 
 
 
 
 
 
 
 
 
So the app is dead - I've made a temporary mirror scraped from archive.org at http://scriptler.banana.management, but once I figure out a reasonable way to auto-populate the metadata for the scripts into groovy comments for scripts without existing metadata-in-comments, I'll be adding everything from the old scriptler repo to the GitHub repo. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-monitor-plugin] (JENKINS-24518) Define different colors to unstable and aborted statuses

[per.oest...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Per Östman commented on  JENKINS-24518 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Define different colors to unstable and aborted statuses  
 
 
 
 
 
 
 
 
 
 
It would also be useful to have a separate color if a build has been claimed - as opposed to today, where claimed builds get the same look as the colorblind mode. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [versionnumber-plugin] (JENKINS-28505) Version Number plugin fails with Java 8

[d.baha...@gmx.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Deniz Bahadir commented on  JENKINS-28505 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Version Number plugin fails with Java 8  
 
 
 
 
 
 
 
 
 
 
Sorry, I am unable to reproduce this behavior. Could you give some more detailed instructions on how to reproduce the NullPointerException (NPE)? 
Did you try the newest 1.6 release of the plugin? Is it fixed by that? 
(Note: The internal format changed from 1.5 to 1.6. Upgrading to 1.6 should work smoothly, but downgrading again might not work without complains. So do not test with your production system.) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-2111) removing a job does not remove the workspace

[nick.volyn...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Volynkin commented on  JENKINS-2111 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: removing a job does not remove the workspace  
 
 
 
 
 
 
 
 
 
 
This happens when you rename a job - its workspace is not renamed and not deleted either. The job page shows the size of the old workspace, but after next build the new workspace will be created and the used space will equal to the sum of two workspaces. When the job is deleted or when you wipe out the workspace, only the new workspace gets deleted. 
Just found that my Jenkins (v 1.635) "stashed" 35GB this way. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [email-ext-plugin] (JENKINS-31177) email notification corrupted due to build failure "FATAL: java.io.IOException: Unexpected termination of the channel"

[slide.o....@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Earl commented on  JENKINS-31177 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: email notification corrupted due to build failure "FATAL: java.io.IOException: Unexpected termination of the channel"  
 
 
 
 
 
 
 
 
 
 
The values are actually replaced by either token macro or core functions. Email-ext doesn't directly replace the values.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-31181) setting slave temporally offline/online not persisted to disk

[asmu...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Asmund Ostvold edited a comment on  JENKINS-31181 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: setting slave temporally offline/online not persisted to disk  
 
 
 
 
 
 
 
 
 
 I have found a solution that works for jenkins-1.635.  { { code:java} diff --git a/core/src/main/java/hudson/model/Computer.java b/core/src/main/java/hudson/model/Computer.javaindex a3ddb20..e76dfdd 100644--- a/core/src/main/java/hudson/model/Computer.java+++ b/core/src/main/java/hudson/model/Computer.java@@ -694,6 +694,14 @@ public /*transient*/ abstract class Computer extends Actionable implements Acces Node node = getNode(); if (node != null) { node.setTemporaryOfflineCause(offlineCause);+   try {+   node.save();+   } catch (IOException e) {+LogRecord lr = new LogRecord(Level.WARNING, "Failed to save temporary offline state change");+lr.setThrown(e);+LOGGER.log(lr);+}+ } synchronized (statusChangeLock) { statusChangeLock.notifyAll(); {code } }   Probably not the correct fix but it works for me. Please feel free to derive work from my diff. I am a long time user of Jenkins but NO Java programmer.  Hope this helps.I have not had the opportunity to test this in the production environment yet. So I do not know if this works for 1.625.1. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.