[JIRA] (JENKINS-56228) Job triggered multiple times by maven dependencies

2019-02-24 Thread amir.schn...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Amir Schnell commented on  JENKINS-56228  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Job triggered multiple times by maven dependencies   
 

  
 
 
 
 

 
 Yes I think this is a good representation  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56116) Commit messages are broken in the CentOS 6 build details - changes

2019-02-24 Thread tasho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arseniy Tashoyan commented on  JENKINS-56116  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Commit messages are broken in the CentOS 6 build details - changes   
 

  
 
 
 
 

 
 After upgrade to RHEL 7 with git 1.8.3.1, the problem disappeared. Thank you for your investigation and help.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56263) Issue in opening web browser when i build the project .

2019-02-24 Thread vineet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vineet Jahagirdar created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56263  
 
 
  Issue in opening web browser when i build the project .   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 browser-axis-plugin, chromedriver-plugin  
 
 
Created: 
 2019-02-25 07:27  
 
 
Environment: 
 Jenkins ver. 2.164,  browser axis 1.0  build timeout 1.19  chrome driver 1.2  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Vineet Jahagirdar  
 

  
 
 
 
 

 
 from webbrowser import open_new_tab url = "" open_new_tab(url)   Above is python script i have written to open browser under build in execute pyhton script.   when i run the same lines of code in my local machine it will open new tab and redirect it to url. But when I build it jenkins it does not redirect and prompts finished successfully  message in the console output.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
   

[JIRA] (JENKINS-56012) stash-pullrequest-builder-plugin variables not seen in multi-configuration jobs unless listed in safeParameters

2019-02-24 Thread plros...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Roskin commented on  JENKINS-56012  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: stash-pullrequest-builder-plugin variables not seen in multi-configuration jobs unless listed in safeParameters   
 

  
 
 
 
 

 
 I tried fixing the issues with the environment. There are multiple issues. One issue that is specific to multi-configuration builds is that StashAditionalParameterEnvironmentContributor#buildEnvironmentFor() uses getCause(StashCause.class). The cause of child builds is the top-level build, not StashCause. That should be considered. That said, it is likely that this issue and JENKINS-51480 would be fixed together.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56262) Upload external test result has issue with ALM15p3 with client type restriction on

2019-02-24 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56262  
 
 
  Upload external test result has issue with ALM15p3 with client type restriction on   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Roy Lu  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2019-02-25 05:58  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Roy Lu  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-55276) HP ALM Plugin - when job is branched only branch appear in HP ALM

2019-02-24 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-55276  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: HP ALM Plugin - when job is branched only branch appear in HP ALM   
 

  
 
 
 
 

 
 Job name is uploaded to a field called 'jenkins-job-name'.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-55264) Threshold Number of tests not working

2019-02-24 Thread bian...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 hubin zhao commented on  JENKINS-55264  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Threshold Number of tests not working   
 

  
 
 
 
 

 
 same question here!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56261) Bitbucket Plugin Auto Trigger All Branches Jobs

2019-02-24 Thread sumit24....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sumit Katiyar created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56261  
 
 
  Bitbucket Plugin Auto Trigger All Branches Jobs   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 bitbucket-plugin  
 
 
Created: 
 2019-02-25 05:06  
 
 
Environment: 
 Production  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Sumit Katiyar  
 

  
 
 
 
 

 
 Hi, After upgraded the Bitbucket plugin we are not able to stop auto indexing, earlier we have stopped by using wrong name in auto deploy option.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 

[JIRA] (JENKINS-56257) Git clone/fetch filtering user:password from git https://user:pwd@path-2-git

2019-02-24 Thread ckr...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chandrasekar Sankarram updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56257  
 
 
  Git clone/fetch filtering user:password from git https://user:pwd@path-2-git   
 

  
 
 
 
 

 
Change By: 
 Chandrasekar Sankarram  
 
 
Summary: 
 Git clone/fetch filtering user:password from git https://user:pwd / @ path-2-git  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56244) NETEASE enterprise account can not to be set in E-mail Notification field

2019-02-24 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum assigned an issue to Adrien Lecharpentier  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56244  
 
 
  NETEASE enterprise account can not to be set in E-mail Notification field   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Component/s: 
 mailer-plugin  
 
 
Component/s: 
 email-ext-plugin  
 
 
Assignee: 
 David van Laatum Adrien Lecharpentier  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56116) Commit messages are broken in the CentOS 6 build details - changes

2019-02-24 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated  JENKINS-56116  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56116  
 
 
  Commit messages are broken in the CentOS 6 build details - changes   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56260) Active Choices Reactive Parameter is showing sometimes empty list

2019-02-24 Thread madhavi.katre...@cgi.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Madhavi Katreddy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56260  
 
 
  Active Choices Reactive Parameter is showing sometimes empty list   
 

  
 
 
 
 

 
Change By: 
 Madhavi Katreddy  
 

  
 
 
 
 

 
 There are some Jenkins jobs with the Active Choices Reactive Parameter list. This list if dynamic list and the values are from the Database table and its is working fine most of the times.Sometimes, this list is showing empty. If Configure    button is clicked followed by apply -> save without changes , its working fine. The operations apply -> save changes the contents of the config.xml file. The main differences are , the before changes config.xml have   and no   element.Attached is for your reference.!image-2019-02-24-20-24-33-369.png!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56260) Active Choices Reactive Parameter is showing sometimes empty list

2019-02-24 Thread madhavi.katre...@cgi.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Madhavi Katreddy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56260  
 
 
  Active Choices Reactive Parameter is showing sometimes empty list   
 

  
 
 
 
 

 
Change By: 
 Madhavi Katreddy  
 
 
Attachment: 
 image-2019-02-24-20-24-33-369.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56260) Active Choices Reactive Parameter is showing sometimes empty list

2019-02-24 Thread madhavi.katre...@cgi.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Madhavi Katreddy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56260  
 
 
  Active Choices Reactive Parameter is showing sometimes empty list   
 

  
 
 
 
 

 
Change By: 
 Madhavi Katreddy  
 

  
 
 
 
 

 
 I have jenkins jobs which There  are  having  some Jenkins jobs with  the Active Choices Reactive Parameter list. This list if dynamic list . The  and the  values are from the Database table and its is working fine most of the times.Sometimes, this list is showing empty. If  I click on  Configure  ->   button is clicked followed by  apply -> save without changes , its working fine.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56260) Active Choices Reactive Parameter is showing sometimes empty list

2019-02-24 Thread madhavi.katre...@cgi.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Madhavi Katreddy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56260  
 
 
  Active Choices Reactive Parameter is showing sometimes empty list   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Bruno P. Kinoshita  
 
 
Components: 
 active-choices-plugin  
 
 
Created: 
 2019-02-25 00:14  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Madhavi Katreddy  
 

  
 
 
 
 

 
 I have jenkins jobs which are having the Active Choices Reactive Parameter list. This list if dynamic list. The values are from the Database table and its is working fine most of the times. Sometimes, this list is showing empty. If I click on Configure -> apply -> save without changes , its working fine.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
  

[JIRA] (JENKINS-56116) Commit messages are broken in the CentOS 6 build details - changes

2019-02-24 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated  JENKINS-56116  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56116  
 
 
  Commit messages are broken in the CentOS 6 build details - changes   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56116) Commit messages are broken in the CentOS 6 build details - changes

2019-02-24 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite started work on  JENKINS-56116  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56116) Commit messages are broken in the CentOS 6 build details - changes

2019-02-24 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56116  
 
 
  Commit messages are broken in the CentOS 6 build details - changes   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Summary: 
 Commit messages are broken in the  CentOS 6  build details - changes  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56151) Include more tags in the xml job to job dsl plugin

2019-02-24 Thread mnr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mohammad Norouzi commented on  JENKINS-56151  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Include more tags in the xml job to job dsl plugin   
 

  
 
 
 
 

 
 Alan Quintiliano Thank you. We have jobs similar to this:   

 

pipelineJob('seed-job') {
  description("Creates all jobs and folders from repositories")
  logRotator(14, -1, -1, -1)
  concurrentBuild(false)
  properties {
disableConcurrentBuilds() // I think this is the same as org.jenkinsci.plugins.workflow.job.properties.DisableConcurrentBuildsJobProperty
disableResume()
  }
  definition {
cps {
  def theScript = new java.io.File('/var/jenkins_home/jobs/seed_job.groovy').text
  script(theScript)
  sandbox()  // Not sure but I think this for 'sandbox' 4th option
}
  }
}
 

 About office365 I can see this in our Jenkins' api doc:      I'm not sure about the 'actions' and trigger jobs property  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56151) Include more tags in the xml job to job dsl plugin

2019-02-24 Thread mnr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mohammad Norouzi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56151  
 
 
  Include more tags in the xml job to job dsl plugin   
 

  
 
 
 
 

 
Change By: 
 Mohammad Norouzi  
 
 
Attachment: 
 image-2019-02-25-10-18-17-715.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-36235) Add optional 'timeout' parameter to 'input' step

2019-02-24 Thread fl...@itnews-bg.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Todorov commented on  JENKINS-36235  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add optional 'timeout' parameter to 'input' step   
 

  
 
 
 
 

 
 I really don't know why is this marked as "fixed". I've opened another ticket about the same issue - https://issues.jenkins-ci.org/browse/JENKINS-56259  It would be really great if there was a parameter for the `input` step. You cannot wrap this in a `timeout` when you are using it at a `stage(){ input {} }` level in a declarative pipeline.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-36235) Add optional 'timeout' parameter to 'input' step

2019-02-24 Thread fl...@itnews-bg.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Todorov edited a comment on  JENKINS-36235  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add optional 'timeout' parameter to 'input' step   
 

  
 
 
 
 

 
 I really don't know why is this marked as "fixed /won't fix ". I've opened another ticket about the same issue - https://issues.jenkins-ci.org/browse/JENKINS-56259 It would be really great if there was a parameter for the `input` step. You cannot wrap this in a `timeout` when you are using it at a `stage()\{ input {} }` level in a declarative pipeline.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56259) Allow input timeout parameter

2019-02-24 Thread fl...@itnews-bg.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Todorov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56259  
 
 
  Allow input timeout parameter   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline, pipeline-input-step-plugin  
 
 
Created: 
 2019-02-24 22:06  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Steve Todorov  
 

  
 
 
 
 

 
 I have been wondering for ages why is there no `timeout` option in the `input` step? I am aware you can wrap your input in a `timeout() {}`, but that is just impossible when you are using the `input` as part of the stage like so:   

 

pipeline {
agent any
stages {
stage('Example') {
input {
message "Should we continue?"
ok "Yes, we should."
submitter "alice,bob"
parameters {
string(name: 'PERSON', defaultValue: 'Mr Jenkins', description: 'Who should I say hello to?')
}
}
steps {
echo "Hello, ${PERSON}, nice to meet you."
}
}
}
} 

   (Taken from https://jenkins.io/blog/2018/04/09/whats-in-declarative/#input)   The possible "workaround" to this would be to create an `input` step in a previous stage which is wrapped in a `timeout` step, but in our case this makes things even more complicated and hard to read.  Are there any plans to include an `timeout` parameter for the `input` step? Maybe something like this (or better?):   

 

input { 
  message "Should we continue?" 
  ok "Yes, we should." 
  submitter "alice,bob" 
  timeout: [time: 1234, unit: 

[JIRA] (JENKINS-55853) Customized Post Build Comment ignored for multi-configuration projects

2019-02-24 Thread plros...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Roskin assigned an issue to Pavel Roskin  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55853  
 
 
  Customized Post Build Comment ignored for multi-configuration projects   
 

  
 
 
 
 

 
Change By: 
 Pavel Roskin  
 
 
Assignee: 
 Pavel Roskin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-55853) Customized Post Build Comment ignored for multi-configuration projects

2019-02-24 Thread plros...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Roskin started work on  JENKINS-55853  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Pavel Roskin  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-55853) Customized Post Build Comment ignored for multi-configuration projects

2019-02-24 Thread plros...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Roskin updated  JENKINS-55853  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55853  
 
 
  Customized Post Build Comment ignored for multi-configuration projects   
 

  
 
 
 
 

 
Change By: 
 Pavel Roskin  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category

2019-02-24 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-44915  
 
 
  Pylint Warnings: Details table could provide summary string with category   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category

2019-02-24 Thread jean_christophe_mo...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Morin commented on  JENKINS-44915  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pylint Warnings: Details table could provide summary string with category   
 

  
 
 
 
 

 
 Exactly.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-55853) Customized Post Build Comment ignored for multi-configuration projects

2019-02-24 Thread plros...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Roskin commented on  JENKINS-55853  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Customized Post Build Comment ignored for multi-configuration projects   
 

  
 
 
 
 

 
 Indeed, it's possible to get the StashPostBuildComment object from the project using getPublishersList(). PR posted: https://github.com/jenkinsci/stash-pullrequest-builder-plugin/pull/43  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category

2019-02-24 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner assigned an issue to Ulli Hafner  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-44915  
 
 
  Pylint Warnings: Details table could provide summary string with category   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Assignee: 
 Ulli Hafner  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category

2019-02-24 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-44915  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pylint Warnings: Details table could provide summary string with category   
 

  
 
 
 
 

 
 That means the text in https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/java/io/jenkins/plugins/analysis/warnings/PyLint.java#L50 is wrong?    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category

2019-02-24 Thread jean_christophe_mo...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Morin commented on  JENKINS-44915  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pylint Warnings: Details table could provide summary string with category   
 

  
 
 
 
 

 
 Though, the output format documented in the UI should be updated to better align with what format the plugin really support.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56182) java.lang.NullPointerException in job when there is no quality gate in Warnings Next Generation Plugin

2019-02-24 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-56182  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException in job when there is no quality gate in Warnings Next Generation Plugin   
 

  
 
 
 
 

 
 mirza zeyrek your NPE is totally different. Please file a new bug report. And please use the released 3.0.3 version (or provide a commit #id) so I can set my workspace to the correct snapshot. The NPE reports that method scanWithTool is on line 492, in the master branch it is at line 576.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56182) java.lang.NullPointerException in job when there is no quality gate in Warnings Next Generation Plugin

2019-02-24 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner edited a comment on  JENKINS-56182  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException in job when there is no quality gate in Warnings Next Generation Plugin   
 

  
 
 
 
 

 
 [~mirza_zeyrek] your NPE is totally different. Please file a new bug report. And please use the released 3.0.3 version (or provide a commit #id) so I can set my workspace to the correct snapshot. The NPE reports that method scanWithTool is on line 492, in the master branch it is at line 576.   Typically, fixing a NPE is quite easy if I have the correct stack trace.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56182) java.lang.NullPointerException in job when there is no quality gate in Warnings Next Generation Plugin

2019-02-24 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56182  
 
 
  java.lang.NullPointerException in job when there is no quality gate in Warnings Next Generation Plugin   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free

2019-02-24 Thread martijnverb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 karianna commented on  JENKINS-54305  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free   
 

  
 
 
 
 

 
 https://api.adoptopenjdk.net is the location you want to pull in versions via our API.  Let me know if you have any issues.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-51672) Ability to get a user's role during build

2019-02-24 Thread jacek.dusze...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacek Duszenko started work on  JENKINS-51672  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jacek Duszenko  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-51672) Ability to get a user's role during build

2019-02-24 Thread jacek.dusze...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacek Duszenko commented on  JENKINS-51672  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to get a user's role during build   
 

  
 
 
 
 

 
 I see that this task is kind of abandoned, so I claim it and am getting to work on it now  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-51672) Ability to get a user's role during build

2019-02-24 Thread jacek.dusze...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacek Duszenko assigned an issue to Jacek Duszenko  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51672  
 
 
  Ability to get a user's role during build   
 

  
 
 
 
 

 
Change By: 
 Jacek Duszenko  
 
 
Assignee: 
 Jacek Duszenko  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category

2019-02-24 Thread jean_christophe_mo...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Morin edited a comment on  JENKINS-44915  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pylint Warnings: Details table could provide summary string with category   
 

  
 
 
 
 

 
 [~drulli], [~mbrekkevold], [~generatz] If I'm not mistaken, this is now solved with the warnings-ng plugin. Using the right {{--msg-template}}, we can now properly make the warnings plugin use the message name for each issue:!image-2019-02-24-14-18-41-831.png|width=553,height=239!Here I used the latest version of warnings-ng (3.0.3) and the --msg-template value given to the pylint command is: "\{path}:\{line}: [\ \ {msg_id}(\ \ {symbol}), \ \ {obj}] \{msg}"  ( without the slashes. I just can't remove them in Jira...)   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category

2019-02-24 Thread jean_christophe_mo...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Morin edited a comment on  JENKINS-44915  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pylint Warnings: Details table could provide summary string with category   
 

  
 
 
 
 

 
 [~drulli], [~mbrekkevold], [~generatz] If I'm not mistaken, this is now solved with the warnings-ng plugin. Using the right {{--msg-template}}, we can now properly make the warnings plugin use the message name for each issue:!image-2019-02-24-14-18-41-831.png|width=553,height=239!Here I used the latest version of warnings-ng (3.0.3) and the --msg-template value given to the pylint command is:  "\  { {{ path}:\{line}: [\{msg_id}(\{symbol}), \{obj}] \{msg} }} "    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category

2019-02-24 Thread jean_christophe_mo...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Morin edited a comment on  JENKINS-44915  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pylint Warnings: Details table could provide summary string with category   
 

  
 
 
 
 

 
 [~drulli], [~mbrekkevold], [~generatz] If I'm not mistaken, this is now solved with the warnings-ng plugin. Using the right {{--msg-template}}, we can now properly make the warnings plugin use the message name for each issue:!image-2019-02-24-14-18-41-831.png|width=553,height=239!Here I used the latest version of warnings-ng (3.0.3) and the --msg-template value given to the pylint command is: "\{path}:\{line}: [\ \ {msg_id}(\ \ {symbol}), \ \ {obj}] \{msg}"   ( without the slashes. I just can't remove them in Jira...)    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category

2019-02-24 Thread jean_christophe_mo...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Morin edited a comment on  JENKINS-44915  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pylint Warnings: Details table could provide summary string with category   
 

  
 
 
 
 

 
 [~drulli] , [~mbrekkevold], [~generatz]   If I'm not mistaken, this is now solved with the warnings-ng plugin. Using the right {{--msg-template}}, we can now properly make the warnings plugin use the message name for each issue:!image-2019-02-24-14-18-41-831.png|width=553,height=239!Here I used the latest version of warnings-ng (3.0.3) and the --msg-template value given to the pylint command is: {{{path}:\{line}: [\{msg_id}(\{symbol}), \{obj}] \{msg}}}   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category

2019-02-24 Thread jean_christophe_mo...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Morin commented on  JENKINS-44915  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pylint Warnings: Details table could provide summary string with category   
 

  
 
 
 
 

 
 Ulli Hafner If I'm not mistaken, this is now solved with the warnings-ng plugin. Using the right --msg-template, we can now properly make the warnings plugin use the message name for each issue:  Here I used the latest version of warnings-ng (3.0.3) and the --msg-template value given to the pylint command is: {{ {path} :{line}: [\{msg_id}(\{symbol}), \{obj}] {msg}}}    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category

2019-02-24 Thread jean_christophe_mo...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Morin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-44915  
 
 
  Pylint Warnings: Details table could provide summary string with category   
 

  
 
 
 
 

 
Change By: 
 Jean-Christophe Morin  
 
 
Attachment: 
 image-2019-02-24-14-18-41-831.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56258) Push to cloud foundry plugin does not consider .cfignore file

2019-02-24 Thread overexcha...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ethashamuddin Mohammed created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56258  
 
 
  Push to cloud foundry plugin does not consider .cfignore file   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 plugin-proposals  
 
 
Created: 
 2019-02-24 17:11  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Ethashamuddin Mohammed  
 

  
 
 
 
 

 
 Upon configuration in .cfignore file to ignore certain files to push, jenkins plugin does not read .cfignore   For this reason, staging of app in pivotal cloud foundry is failing.   Please help on this.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 

[JIRA] (JENKINS-56257) Git clone/fetch filtering user:password from git https://user:pwd/path-2-git

2019-02-24 Thread ckr...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chandrasekar Sankarram created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56257  
 
 
  Git clone/fetch filtering user:password from git https://user:pwd/path-2-git   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2019-02-24 16:50  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Chandrasekar Sankarram  
 

  
 
 
 
 

 
 CliGitApiImpl fetch method is not binding git fetch url correctly, URIished url is binding the args by filtering the user:password in the url with call to url.toString() as against url.toPrivateString() to allow the original url to be passed through. It is understood for some git access command like commit can potentially cause issue; and it is valid to filter the user:password for special situation and enforce the security via credentials binding routes. Fix is identified and isolated to CliGitApiImpl FetchCommand fetch_() execute method and url binding to args list around line 454 in current version is: args.add(url); and to be revised as          args.add(url.toPrivateString());        Above revision will benefit for scenarios when we create seeding jobs to create another job and pass it parameters. This will also relieve the need to setup credentials in jenkins globally and the callers url is respected for the processing   Thanks Sankar    
 

  
 
 
 
 

 
 
 

 
 
   

[JIRA] (JENKINS-56257) Git clone/fetch filtering user:password from git https://user:pwd/path-2-git

2019-02-24 Thread ckr...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chandrasekar Sankarram created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56257  
 
 
  Git clone/fetch filtering user:password from git https://user:pwd/path-2-git   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2019-02-24 16:50  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Chandrasekar Sankarram  
 

  
 
 
 
 

 
 CliGitApiImpl fetch method is not binding git fetch url correctly, URIished url is binding the args by filtering the user:password in the url with call to url.toString() as against url.toPrivateString() to allow the original url to be passed through. It is understood for some git access command like commit can potentially cause issue; and it is valid to filter the user:password for special situation and enforce the security via credentials binding routes. Fix is identified and isolated to CliGitApiImpl FetchCommand fetch_() execute method and url binding to args list around line 454 in current version is: args.add(url); and to be revised as          args.add(url.toPrivateString());        Above revision will benefit for scenarios when we create seeding jobs to create another job and pass it parameters. This will also relieve the need to setup credentials in jenkins globally and the callers url is respected for the processing   Thanks Sankar    
 

  
 
 
 
 

 
 
 

 
 
   

[JIRA] (JENKINS-56182) java.lang.NullPointerException in job when there is no quality gate in Warnings Next Generation Plugin

2019-02-24 Thread mirza_zey...@mersinuni.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 mirza zeyrek edited a comment on  JENKINS-56182  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException in job when there is no quality gate in Warnings Next Generation Plugin   
 

  
 
 
 
 

 
 *EDIT: Issue of not having options available in static analysis tool section solved by uninstalling all related plug-ins 1 by 1 and installing next generation plug-in only.**Also found a workaround for Null Pointer Exception. Looks like this tend to happen for newly setup jobs which does not have previous failed jobs. So, you need to make 1st job pass. For this set health gate threshold more than existing warning count. Issue still occurs with latest HPI from Jenkins master - #200* I have similar issue. [~drulli] Also Static Analysis Tools select box is empty on freestyle job. !image-2019-02-24-15-45-48-530.png!ERROR: Build step failed with exception java.lang.NullPointerException at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.scanWithTool(IssuesRecorder.java:492) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:481) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.perform(IssuesRecorder.java:455) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1835) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Build step 'Record static analysis results' marked build as failure Finished: FAILUREHere is the installed plug-in versions:!image-2019-02-24-15-58-01-960.png!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

[JIRA] (JENKINS-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API

2019-02-24 Thread nisshah1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55829  
 
 
  Expose AbstractCIBase#disabledAdministrativeMonitors as internal API   
 

  
 
 
 
 

 
Change By: 
 Nisarg Shah  
 
 
Comment: 
 [~oleg_nenashev]So do I need to return extra new empty container from the getter method? Is this what you are suggesting?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56182) java.lang.NullPointerException in job when there is no quality gate in Warnings Next Generation Plugin

2019-02-24 Thread mirza_zey...@mersinuni.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 mirza zeyrek edited a comment on  JENKINS-56182  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException in job when there is no quality gate in Warnings Next Generation Plugin   
 

  
 
 
 
 

 
 I have similar issue.  [~drulli]  Also Static Analysis Tools select box is empty on freestyle job.   !image-2019-02-24-15-45-48-530.png!ERROR: Build step failed with exceptionjava.lang.NullPointerException at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.scanWithTool(IssuesRecorder.java:492) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:481) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.perform(IssuesRecorder.java:455) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1835) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Build step 'Record static analysis results' marked build as failureFinished: FAILURE Here is the installed plug-in versions:!image-2019-02-24-15-58-01-960.png!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56182) java.lang.NullPointerException in job when there is no quality gate in Warnings Next Generation Plugin

2019-02-24 Thread mirza_zey...@mersinuni.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 mirza zeyrek commented on  JENKINS-56182  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException in job when there is no quality gate in Warnings Next Generation Plugin   
 

  
 
 
 
 

 
 I have similar issue. Also Static Analysis Tools select box is empty on freestyle job.  ERROR: Build step failed with exception java.lang.NullPointerException at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.scanWithTool(IssuesRecorder.java:492) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:481) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.perform(IssuesRecorder.java:455) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1835) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Build step 'Record static analysis results' marked build as failure Finished: FAILURE  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-56182) java.lang.NullPointerException in job when there is no quality gate in Warnings Next Generation Plugin

2019-02-24 Thread mirza_zey...@mersinuni.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 mirza zeyrek updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56182  
 
 
  java.lang.NullPointerException in job when there is no quality gate in Warnings Next Generation Plugin   
 

  
 
 
 
 

 
Change By: 
 mirza zeyrek  
 
 
Attachment: 
 image-2019-02-24-15-45-48-530.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-55853) Customized Post Build Comment ignored for multi-configuration projects

2019-02-24 Thread plros...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Roskin commented on  JENKINS-55853  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Customized Post Build Comment ignored for multi-configuration projects   
 

  
 
 
 
 

 
 I tried to fix the issue, but my knowledge of Jenkins internals is insufficient. Let's me just describe where I stopped. One approach is to introduce a dependency on the Matrix plugin. email-ext-plugins is an example of such code. It can select whether the post-build action happens in child builds, in the top-level build or in both. But I would rather avoid adding a dependency. I believe that StashPostBuildComment.perform() is not the best place to publish the configuration of StashPostBuildComment, as it happens in a child build. But I've noticed getRootProject() and getRootBuild(), I'll see if they would help. A cleaner approach would be to examine the project for an object of the given class, just like it's done for the trigger. StashBuild.onCompleted() calls StashBuildTrigger.getTrigger(build.getProject()), which is implemented using project's getTrigger(). That would make it possible to read the StashPostBuildComment configuration from the project. But I don't see such method for post-build actions. Another approach would be to make StashPostBuildComment listen to some event that happens for the top-level build and publish its configuration with addAction to that build.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.