[JIRA] (JENKINS-41724) Cannot pull from bitbucket

2017-02-06 Thread dimakie...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dmytro Zhernosiekov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41724  
 
 
  Cannot pull from bitbucket   
 

  
 
 
 
 

 
Change By: 
 Dmytro Zhernosiekov  
 

  
 
 
 
 

 
 Hi,I'm upload machine ssh key in bitbucket. Create Job in Jenkins to pull repo. In job I could see that it connect to bitbucket did fetch, but cannot pull with error that cannot checkout to branch. Is it bug or I did something wrong? {quote} Building in workspace /var/lib/jenkins/workspace/pis > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url g...@bitbucket.org:company/code.git # timeout=10Fetching upstream changes from g...@bitbucket.org:company/code.git > git --version # timeout=10using GIT_SSH to set credentials  > git fetch --tags --progress g...@bitbucket.org:company/code.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/develop^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10Checking out Revision 968c691e3c56dd685cd6907f657c82d159ae21bc (refs/remotes/origin/develop) > git config core.sparsecheckout # timeout=10 > git checkout -f 968c691e3c56dd685cd6907f657c82d159ae21bc > git rev-list 968c691e3c56dd685cd6907f657c82d159ae21bc # timeout=10[pis] $ /bin/sh -xe /tmp/hudson4526651168464598726.sh+ git pullYou are not currently on a branch. Please specify whichbranch you want to merge with. See git-pull(1) for details.git pull  Build step 'Execute shell' marked build as failureFinished: FAILURE {quote}When I tried to fetch repo from cli:{quote}[user@user.ansible:~]$ git clone g...@bitbucket.org:company/code.git pisCloning into 'code'...remote: Counting objects: 4936, done.remote: Compressing objects: 100% (2826/2826), done.remote: Total 4936 (delta 3292), reused 3300 (delta 2086)Receiving objects: 100% (4936/4936), 3.18 MiB | 2.75 MiB/s, done.Resolving deltas: 100% (3292/3292), done.[user@user.ansible:~]$ cd code/[user@user.ansible:~/code]$ git fetch --allFetching origin[user@user.ansible:~/code]$ git checkout developAlready on 'develop'[user@user.ansible:~/code]$ git pullAlready up-to-date.[user@user.ansible:~/code]$ {quote}Since Jenkins has /bin/false bash, I cannot do the same for Jenkins user in CLI, but I pus the same key in $JENKINS_HOME/.ssh folder. md5 code:{quote}[user@user.ansible:~]$ md5sum .ssh/id_rsaf3bcfc4ad1abdac352b49e77909b56c8  .ssh/id_rsa[user@user.ansible:~]$ sudo md5sum /var/lib/jenkins/.ssh/id_rsaf3bcfc4ad1abdac352b49e77909b56c8  /var/lib/jenkins/.ssh/id_rsa{quote}The way I point on branch in Jenkins:*/developCould you check this issue please?  
 

  
 
 
 
 

 
 

[JIRA] (JENKINS-41689) Unable to download S3 artifact from link

2017-02-06 Thread mr.akbas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander A commented on  JENKINS-41689  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to download S3 artifact from link   
 

  
 
 
 
 

 
 Do you publish to two different buckets in one pipeline script? If yes, in this case I will investigate https://github.com/jenkinsci/s3-plugin/pull/97. If you are publishing only to one bucket, I will check https://github.com/jenkinsci/s3-plugin/pull/100. Did you try to follow: 
 
Even if most of the features of the Jenkins S3 Plugin require the user to specify the target region, some feature rely on a default Amazon S3 region which is by default the "US Standard Amazon S3 Region" and its endpoint s3.amazonaws.com. This default region can be overridden with the system property hudson.plugins.s3.DEFAULT_AMAZON_S3_REGION. Note that this default region name MUST match with a region define in the AWS SDK configuration file endpoints.json (see above).
 from https://github.com/jenkinsci/s3-plugin (Usage) And the last question, please, try 0.10.10. Does it work for you? Br, Alex  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41301) Show cog (⚙) to the right of search/help in the top banner

2017-02-06 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-41301  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Show cog (⚙) to the right of search/help in the top banner   
 

  
 
 
 
 

 
 

What I'm suggesting is to do the same for jenkins
 Since the bread crumb bar has a context menu that includes all of Manage Jenkins, and appears when clicking the down arrow to its right, this seems redundant.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41645) Better error messages when illegal identifiers are used in an `environment` block

2017-02-06 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-41645  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Better error messages when illegal identifiers are used in an `environment` block   
 

  
 
 
 
 

 
 Argh, I only actually did the check for being a valid Java identifier - https://github.com/jenkinsci/pipeline-model-definition-plugin/commit/e3d0a948f28975a595f41d0749907c788bfb0306 - that was relevant when coming from the JSON. D'oh.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41645) Better error messages when illegal identifiers are used in an `environment` block

2017-02-06 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-41645  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Better error messages when illegal identifiers are used in an `environment` block   
 

  
 
 
 
 

 
 Ok, 456_XYZ I can't do anything about - that's a Groovy compilation error, so it's happening before we get to the linting.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41645) Better error messages when illegal identifiers are used in an `environment` block

2017-02-06 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-41645  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Better error messages when illegal identifiers are used in an `environment` block   
 

  
 
 
 
 

 
 Same with what-about-hyphens. Boo.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-40851) Sheets component

2017-02-06 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40851  
 
 
  Sheets component   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Priority: 
 Critical Minor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41645) Better error messages when illegal identifiers are used in an `environment` block

2017-02-06 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-41645  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Better error messages when illegal identifiers are used in an `environment` block   
 

  
 
 
 
 

 
 Ok, I did do the check right, I'm just not reporting it right. Oy.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41724) Cannot pull from bitbucket

2017-02-06 Thread dimakie...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dmytro Zhernosiekov commented on  JENKINS-41724  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot pull from bitbucket   
 

  
 
 
 
 

 
 Checked that bitbucket is added to known_host to be sure no issue with SSH: 

bitbucket.org,104.192.143.2 ssh-rsa B3NzaC1yc2EBIwAAAQEAubiN81eDcafrgMeLzaFPsw2kNvEcqTKl/VqLat/MaB33pZy0y3rJZtnqwR2qOOvbwKZYKiEO1O6VqNEBxKvJJelCq0dTXWT5pbO2gDXC6h6QDXCaHo6pOHGPUy+YBaGQRGuSusMEASYiWunYN0vCAI8QaXnWMXNMdFP3jHAJH0eDsoiGnLPBlBp4TNm6rYI74nMzgz3B9IikW4WVK+dc8KZJZWYjAuORU3jc1c/NPskD2ASinf8v3xnfXeukU0sJ5N6m5E8VLjObPEO+mN2t/FZTMZLiFqPWc/ALSqnMnnhwrNi2rbfg/rd/IpL8Le3pSBne8+seeFVBoGqzHM9yXw== 104.192.143.3 ssh-rsa B3NzaC1yc2EBIwAAAQEAubiN81eDcafrgMeLzaFPsw2kNvEcqTKl/VqLat/MaB33pZy0y3rJZtnqwR2qOOvbwKZYKiEO1O6VqNEBxKvJJelCq0dTXWT5pbO2gDXC6h6QDXCaHo6pOHGPUy+YBaGQRGuSusMEASYiWunYN0vCAI8QaXnWMXNMdFP3jHAJH0eDsoiGnLPBlBp4TNm6rYI74nMzgz3B9IikW4WVK+dc8KZJZWYjAuORU3jc1c/NPskD2ASinf8v3xnfXeukU0sJ5N6m5E8VLjObPEO+mN2t/FZTMZLiFqPWc/ALSqnMnnhwrNi2rbfg/rd/IpL8Le3pSBne8+seeFVBoGqzHM9yXw== 104.192.143.1 ssh-rsa B3NzaC1yc2EBIwAAAQEAubiN81eDcafrgMeLzaFPsw2kNvEcqTKl/VqLat/MaB33pZy0y3rJZtnqwR2qOOvbwKZYKiEO1O6VqNEBxKvJJelCq0dTXWT5pbO2gDXC6h6QDXCaHo6pOHGPUy+YBaGQRGuSusMEASYiWunYN0vCAI8QaXnWMXNMdFP3jHAJH0eDsoiGnLPBlBp4TNm6rYI74nMzgz3B9IikW4WVK+dc8KZJZWYjAuORU3jc1c/NPskD2ASinf8v3xnfXeukU0sJ5N6m5E8VLjObPEO+mN2t/FZTMZLiFqPWc/ALSqnMnnhwrNi2rbfg/rd/IpL8Le3pSBne8+seeFVBoGqzHM9yXw==
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you a

[JIRA] (JENKINS-39086) Scan Credentials dropdown is always empty

2017-02-06 Thread fe...@debuggable.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Felix Geisendörfer commented on  JENKINS-39086  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Scan Credentials dropdown is always empty   
 

  
 
 
 
 

 
 Same issue. Re-creating the credential as username/password worked. But it's very confusing ...  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41742) Integrate changes for the 2.45 release

2017-02-06 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41742  
 
 
  Integrate changes for the 2.45 release   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 core  
 
 
Created: 
 2017/Feb/06 8:30 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group

[JIRA] (JENKINS-41741) wrong parameters order with Jenkins Parameterized Trigger plugin

2017-02-06 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker commented on  JENKINS-41741  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: wrong parameters order with Jenkins Parameterized Trigger plugin   
 

  
 
 
 
 

 
 Provide a short DSL script that reproduces your problem.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41741) wrong parameters order with Jenkins Parameterized Trigger plugin

2017-02-06 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41741  
 
 
  wrong parameters order with Jenkins Parameterized Trigger plugin   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Priority: 
 Blocker Minor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41744) Improve the supportability of the AD plugin

2017-02-06 Thread fbelz...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Félix Belzunce Arcos created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41744  
 
 
  Improve the supportability of the AD plugin   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Félix Belzunce Arcos  
 
 
Components: 
 active-directory-plugin  
 
 
Created: 
 2017/Feb/06 8:35 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Félix Belzunce Arcos  
 

  
 
 
 
 

 
 As a Jenkins admin I would like to: 1. List all the servers/domain controllers exposed by the GC/LDAP Catalog on a Active Directory domain  2. Check if a Domain Controller is broken 3. Check the latency of a Domain Controller  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 

[JIRA] (JENKINS-41743) Gitlab org folder support

2017-02-06 Thread k...@kohsuke.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kohsuke Kawaguchi created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41743  
 
 
  Gitlab org folder support   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Robin Müller  
 
 
Components: 
 gitlab-plugin  
 
 
Created: 
 2017/Feb/06 8:35 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Kohsuke Kawaguchi  
 

  
 
 
 
 

 
 During FOSDEM, a number of people walked up to us and wanted to see the org folder support for GitLab. Internally, this means we need to write gitlab branch source, either as a separate plugin or in the existing plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was

[JIRA] (JENKINS-41743) Gitlab org folder support

2017-02-06 Thread k...@kohsuke.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kohsuke Kawaguchi assigned an issue to Kohsuke Kawaguchi  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41743  
 
 
  Gitlab org folder support   
 

  
 
 
 
 

 
Change By: 
 Kohsuke Kawaguchi  
 
 
Assignee: 
 Robin Müller Kohsuke Kawaguchi  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41253) build parameter not usable in Docker build step

2017-02-06 Thread greg...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Grégoire Bellon-Gervais commented on  JENKINS-41253  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: build parameter not usable in Docker build step   
 

  
 
 
 
 

 
 Hello, we encountered the same issue  

 
SEVERE: Error during callback
com.github.dockerjava.api.exception.InternalServerErrorException: {"message":"Error parsing reference: \":5043//:$ID\" is not a valid repository/tag: invalid reference format"}

at com.github.dockerjava.jaxrs.filter.ResponseStatusExceptionFilter.filter(ResponseStatusExceptionFilter.java:53)
at org.glassfish.jersey.client.ClientFilteringStages$ResponseFilterStage.apply(ClientFilteringStages.java:140)
at org.glassfish.jersey.client.ClientFilteringStages$ResponseFilterStage.apply(ClientFilteringStages.java:128)
at org.glassfish.jersey.process.internal.Stages.process(Stages.java:171)
at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:257)
at org.glassfish.jersey.client.JerseyInvocation$2.call(JerseyInvocation.java:701)
at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
at org.glassfish.jersey.internal.Errors.process(Errors.java:228)
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:444)
at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:697)
at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:448)
at org.glassfish.jersey.client.JerseyInvocation$Builder.post(JerseyInvocation.java:349)
at com.github.dockerjava.jaxrs.async.POSTCallbackNotifier.response(POSTCallbackNotifier.java:29)
at com.github.dockerjava.jaxrs.async.AbstractCallbackNotifier.call(AbstractCallbackNotifier.java:50)
at com.github.dockerjava.jaxrs.async.AbstractCallbackNotifier.call(AbstractCallbackNotifier.java:24)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Feb 05, 2017 9:41:32 PM org.jenkinsci.plugins.dockerbuildstep.DockerBuilder perform
SEVERE: Failed to execute Docker command Push image: {"message":"Error parsing reference: \":5043//:$ID\" is not a valid repository/tag: invalid reference format"}
 

 Rolling back to 1.35 fixes the issue. We are under apache tomcat 7.0.59 with oracle java 1.8.0_111 and docker 1.13.0-0~debian-wheezy. Jenkins is 1.651.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  

[JIRA] (JENKINS-41659) Stabilise ATH

2017-02-06 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-41659  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Stabilise ATH   
 

  
 
 
 
 

 
 I slightly changed that test, but it just happens elsewhere "waitForJobRun.." is called - never gets the callback, infinitely subscribes and waits.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41640) Scroll spy improvements

2017-02-06 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-41640  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Scroll spy improvements   
 

  
 
 
 
 

 
 Code changed in jenkins User: Andrew Bayer Path: .github/PULL_REQUEST_TEMPLATE.md http://jenkins-ci.org/commit/pipeline-model-definition-plugin/46fe30775bb1924f32873ce30e021d4db5c4fa50 Log: [FIXED JENKINS-41640] Add a PR template  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41640) Scroll spy improvements

2017-02-06 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41640  
 
 
  Scroll spy improvements   
 

  
 
 
 
 

 
Change By: 
 SCM/JIRA link daemon  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41253) build parameter not usable in Docker build step

2017-02-06 Thread greg...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Grégoire Bellon-Gervais commented on  JENKINS-41253  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: build parameter not usable in Docker build step   
 

  
 
 
 
 

 
 For test purpose, I have tried to put a backslash in front of my parameter ($ID) in the field "Name of the image to tag (repository/image:tag)" for tag command : "/:\$ID" But I still got an error even if this time, the $ID is correctly replaced : 

 
Feb 05, 2017 9:42:38 PM org.jenkinsci.plugins.dockerbuildstep.DockerBuilder perform
SEVERE: Failed to execute Docker command Tag image: {"message":"Error parsing reference: \"/:\\\"37c3adc3454bd0eb1b24a9974d78a4efda5077a0\\\"\" is not a valid repository/tag: invalid reference format"}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41610) Add a pull request template and contributing.md to pipeline-model-definition-plugin.git

2017-02-06 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41610  
 
 
  Add a pull request template and contributing.md to pipeline-model-definition-plugin.git   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41659) Stabilise ATH

2017-02-06 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale edited a comment on  JENKINS-41659  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Stabilise ATH   
 

  
 
 
 
 

 
 I slightly changed that test, but it just happens elsewhere "waitForJobRun.." is called - never gets the callback, infinitely subscribes and waits.  [~cliffmeyers] well that is the point - that call back specifically waits for the SSE event before it fires.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41705) Unable to install bitbucket-branch-source 2.0.2 due to broken dependency

2017-02-06 Thread costescuand...@skymail.ro (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrei Costescu commented on  JENKINS-41705  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to install bitbucket-branch-source 2.0.2 due to broken dependency   
 

  
 
 
 
 

 
 I got the same problem after doing a routine upgrade last week on the standard stable jenkins 2.x build. Now it always complains in "Manage Jenkins" that: 

 
There are dependency errors loading some plugins: 
GitHub Branch Source Plugin v2.0.1 
SCM API Plugin v1.3 is older than required. To fix, install v2.0.2 or later.
GitHub Organization Folder Plugin v1.5 
GitHub Branch Source Plugin v1.9 failed to load. Fix this plugin first. 

 And indeed le plugin's page lists 1.3 as latest. I can't upgrade the plugin. And can't downgrade the other plugins either nicely because they fail to load. I could manually remove the plugins from disk but I prefer waiting for a compatible version of SCM API plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41659) Stabilise ATH

2017-02-06 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale edited a comment on  JENKINS-41659  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Stabilise ATH   
 

  
 
 
 
 

 
 I slightly changed that test, but it just happens elsewhere "waitForJobRun.." is called - never gets the callback, infinitely subscribes and waits. [~cliffmeyers] well that is the point - that call back specifically waits for the SSE event before it fires.  And it doesn't consistently fail to fire. Locally for me it mostly seems to work. Well depends on the day of the week. Mood etc.
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41705) Unable to install bitbucket-branch-source 2.0.2 due to broken dependency

2017-02-06 Thread costescuand...@skymail.ro (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrei Costescu edited a comment on  JENKINS-41705  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to install bitbucket-branch-source 2.0.2 due to broken dependency   
 

  
 
 
 
 

 
 I got the same problem after doing a routine upgrade last week on the standard stable jenkins 2.x build. Now it always complains in "Manage Jenkins" that:{noformat}There are dependency errors loading some plugins: GitHub Branch Source Plugin v2.0.1 SCM API Plugin v1.3 is older than required. To fix, install v2.0.2 or later.GitHub Organization Folder Plugin v1.5 GitHub Branch Source Plugin v1.9 failed to load. Fix this plugin first.{noformat}And indeed  le  the  plugin's page lists 1.3 as latest. I can't upgrade the plugin. And can't downgrade the other plugins either nicely because they fail to load. I could manually remove the plugins from disk but I prefer waiting for a compatible version of SCM API plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41253) build parameter not usable in Docker build step

2017-02-06 Thread greg...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Grégoire Bellon-Gervais updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41253  
 
 
  build parameter not usable in Docker build step   
 

  
 
 
 
 

 
Change By: 
 Grégoire Bellon-Gervais  
 
 
Comment: 
 Hello,we encountered the same issue {noformat}SEVERE: Error during callbackcom.github.dockerjava.api.exception.InternalServerErrorException: {"message":"Error parsing reference: \":5043//:$ID\" is not a valid repository/tag: invalid reference format"}at com.github.dockerjava.jaxrs.filter.ResponseStatusExceptionFilter.filter(ResponseStatusExceptionFilter.java:53)at org.glassfish.jersey.client.ClientFilteringStages$ResponseFilterStage.apply(ClientFilteringStages.java:140)at org.glassfish.jersey.client.ClientFilteringStages$ResponseFilterStage.apply(ClientFilteringStages.java:128)at org.glassfish.jersey.process.internal.Stages.process(Stages.java:171)at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:257)at org.glassfish.jersey.client.JerseyInvocation$2.call(JerseyInvocation.java:701)at org.glassfish.jersey.internal.Errors.process(Errors.java:315)at org.glassfish.jersey.internal.Errors.process(Errors.java:297)at org.glassfish.jersey.internal.Errors.process(Errors.java:228)at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:444)at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:697)at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:448)at org.glassfish.jersey.client.JerseyInvocation$Builder.post(JerseyInvocation.java:349)at com.github.dockerjava.jaxrs.async.POSTCallbackNotifier.response(POSTCallbackNotifier.java:29)at com.github.dockerjava.jaxrs.async.AbstractCallbackNotifier.call(AbstractCallbackNotifier.java:50)at com.github.dockerjava.jaxrs.async.AbstractCallbackNotifier.call(AbstractCallbackNotifier.java:24)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)at java.lang.Thread.run(Thread.java:745)Feb 05, 2017 9:41:32 PM org.jenkinsci.plugins.dockerbuildstep.DockerBuilder performSEVERE: Failed to execute Docker command Push image: {"message":"Error parsing reference: \":5043//:$ID\" is not a valid repository/tag: invalid reference format"}{noformat}Rolling back to 1.35 fixes the issue.We are under apache tomcat 7.0.59 with oracle java 1.8.0_111 and docker 1.13.0-0~debian-wheezy.Jenkins is 1.651.3  
 

  
 
 
 
 

 
 
 

 
 

[JIRA] (JENKINS-41080) java.lang.IllegalStateException: The template variable has no value - since 1.37

2017-02-06 Thread greg...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Grégoire Bellon-Gervais commented on  JENKINS-41080  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.IllegalStateException: The template variable has no value - since 1.37   
 

  
 
 
 
 

 
 Hello, we encountered the same issue  

 
SEVERE: Error during callback
com.github.dockerjava.api.exception.InternalServerErrorException: {"message":"Error parsing reference: \":5043//:$ID\" is not a valid repository/tag: invalid reference format"}

at com.github.dockerjava.jaxrs.filter.ResponseStatusExceptionFilter.filter(ResponseStatusExceptionFilter.java:53)
at org.glassfish.jersey.client.ClientFilteringStages$ResponseFilterStage.apply(ClientFilteringStages.java:140)
at org.glassfish.jersey.client.ClientFilteringStages$ResponseFilterStage.apply(ClientFilteringStages.java:128)
at org.glassfish.jersey.process.internal.Stages.process(Stages.java:171)
at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:257)
at org.glassfish.jersey.client.JerseyInvocation$2.call(JerseyInvocation.java:701)
at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
at org.glassfish.jersey.internal.Errors.process(Errors.java:228)
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:444)
at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:697)
at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:448)
at org.glassfish.jersey.client.JerseyInvocation$Builder.post(JerseyInvocation.java:349)
at com.github.dockerjava.jaxrs.async.POSTCallbackNotifier.response(POSTCallbackNotifier.java:29)
at com.github.dockerjava.jaxrs.async.AbstractCallbackNotifier.call(AbstractCallbackNotifier.java:50)
at com.github.dockerjava.jaxrs.async.AbstractCallbackNotifier.call(AbstractCallbackNotifier.java:24)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Feb 05, 2017 9:41:32 PM org.jenkinsci.plugins.dockerbuildstep.DockerBuilder perform
SEVERE: Failed to execute Docker command Push image: {"message":"Error parsing reference: \":5043//:$ID\" is not a valid repository/tag: invalid reference format"}
 

 Rolling back to 1.35 fixes the issue. We are under apache tomcat 7.0.59 with oracle java 1.8.0_111 and docker 1.13.0-0~debian-wheezy. Jenkins is 1.651.3  
 

  
 
 
 
 

 
 
 

 
 
  

[JIRA] (JENKINS-41080) java.lang.IllegalStateException: The template variable has no value - since 1.37

2017-02-06 Thread greg...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Grégoire Bellon-Gervais commented on  JENKINS-41080  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.IllegalStateException: The template variable has no value - since 1.37   
 

  
 
 
 
 

 
 For test purpose, I have tried to put a backslash in front of my parameter ($ID) in the field "Name of the image to tag (repository/image:tag)" for tag command : "/:\$ID" But I still got an error even if this time, the $ID is correctly replaced : 

 
Feb 05, 2017 9:42:38 PM org.jenkinsci.plugins.dockerbuildstep.DockerBuilder perform
SEVERE: Failed to execute Docker command Tag image: {"message":"Error parsing reference: \"/:\\\"37c3adc3454bd0eb1b24a9974d78a4efda5077a0\\\"\" is not a valid repository/tag: invalid reference format"}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41253) build parameter not usable in Docker build step

2017-02-06 Thread greg...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Grégoire Bellon-Gervais updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41253  
 
 
  build parameter not usable in Docker build step   
 

  
 
 
 
 

 
Change By: 
 Grégoire Bellon-Gervais  
 
 
Comment: 
 For test purpose, I have tried to put a backslash in front of my parameter ($ID) in the field "Name of the image to tag (repository/image:tag)" for tag command : "/:\$ID"But I still got an error even if this time, the $ID is correctly replaced :{noformat}Feb 05, 2017 9:42:38 PM org.jenkinsci.plugins.dockerbuildstep.DockerBuilder performSEVERE: Failed to execute Docker command Tag image: {"message":"Error parsing reference: \"/:\\\"37c3adc3454bd0eb1b24a9974d78a4efda5077a0\\\"\" is not a valid repository/tag: invalid reference format"}{noformat}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41645) Better error messages when illegal identifiers are used in an `environment` block

2017-02-06 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-41645  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Better error messages when illegal identifiers are used in an `environment` block   
 

  
 
 
 
 

 
 PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/106  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41645) Better error messages when illegal identifiers are used in an `environment` block

2017-02-06 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-41645  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41645  
 
 
  Better error messages when illegal identifiers are used in an `environment` block   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41645) Better error messages when illegal identifiers are used in an `environment` block

2017-02-06 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer started work on  JENKINS-41645  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41668) No way to specify directory for dockerfile

2017-02-06 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer started work on  JENKINS-41668  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41668) No way to specify directory for dockerfile

2017-02-06 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-41668  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: No way to specify directory for dockerfile   
 

  
 
 
 
 

 
 Initial PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/107  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41668) No way to specify directory for dockerfile

2017-02-06 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-41668  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41668  
 
 
  No way to specify directory for dockerfile   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-36581) Jenkins CLI delete-builds command doesn't exit

2017-02-06 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36581  
 
 
  Jenkins CLI delete-builds command doesn't exit   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Summary: 
 Jenkins CLIdelete-builds command doesn't exit  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41349) Post-FOSDEM 2017 Hackathon

2017-02-06 Thread k...@kohsuke.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kohsuke Kawaguchi commented on  JENKINS-41349  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Post-FOSDEM 2017 Hackathon   
 

  
 
 
 
 

 
 Hackathon live doc is http://bit.ly/2kcvceb  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-7791) CLI authenticated mode not working

2017-02-06 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-7791  
 
 
  CLI authenticated mode not working   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-38736) update guice to release version

2017-02-06 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38736  
 
 
  update guice to release version   
 

  
 
 
 
 

 
Change By: 
 Arnaud Héritier  
 
 
Resolution: 
 Done  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41705) Unable to install bitbucket-branch-source 2.0.2 due to broken dependency

2017-02-06 Thread emil.sty...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Emil Styrke commented on  JENKINS-41705  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to install bitbucket-branch-source 2.0.2 due to broken dependency   
 

  
 
 
 
 

 
 Andrei Costescu: The GitHub issue was due to a typo - see https://issues.jenkins-ci.org/browse/JENKINS-41661?focusedCommentId=286164&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-286164 for background and how to fix it.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41745) Remoting-free CLI

2017-02-06 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41745  
 
 
  Remoting-free CLI   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 cli, core  
 
 
Created: 
 2017/Feb/06 8:52 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Daniel Beck  
 

  
 
 
 
 

 
 Followup to the November 2016 security fix. We need ideas for making the CLI less (not?) vulnerable to that kind of exploit. https://groups.google.com/d/msg/jenkinsci-dev/ijnIr8LhBG0/tM4Jc39cDgAJ (public) https://groups.google.com/d/msg/jenkinsci-cert/3dnPu7x88a8/7JwwMKj7BgAJ (Jenkins CERT private)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 

[JIRA] (JENKINS-41640) Scroll spy improvements

2017-02-06 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41640  
 
 
  Scroll spy improvements   
 

  
 
 
 
 

 
Change By: 
 Tom FENNELLY  
 

  
 
 
 
 

 
 Post  2  1 .0 need to revisit scrollspy in classic for some overdue fixes: https://github.com/jenkinsci/jenkins/pull/2339Not really a blue ocean task per se, but putting here to plan for it as it is needed post 1.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41746) Extensible validation for WithScripts in Declarative

2017-02-06 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41746  
 
 
  Extensible validation for WithScripts in Declarative   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Andrew Bayer  
 
 
Components: 
 pipeline-model-definition-plugin  
 
 
Created: 
 2017/Feb/06 8:55 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Andrew Bayer  
 

  
 
 
 
 

 
 On JENKINS-41668, I'm realizing I'd like to have validation of, in this case, whether the Dockerfile name contains a directory name as well. I could theoretically bake that into ModelValidatorImpl directly, but that's not ideal, so I'd like to see something connected to our extension points (specifically WithScript and its descendants) that allows providing additional validation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
  

[JIRA] (JENKINS-41640) Scroll spy improvements

2017-02-06 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Auto closed in error. A commit must have had the wrong JIRA on it.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41640  
 
 
  Scroll spy improvements   
 

  
 
 
 
 

 
Change By: 
 Tom FENNELLY  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41747) Display statuses on the organization dashboard page

2017-02-06 Thread vinc...@massol.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Massol updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41747  
 
 
  Display statuses on the organization dashboard page   
 

  
 
 
 
 

 
Change By: 
 Vincent Massol  
 
 
Summary: 
 Display statuses on the  organization  dashboard page  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41747) Display statuses on the dashboard page

2017-02-06 Thread vinc...@massol.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Massol created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41747  
 
 
  Display statuses on the dashboard page   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Attachments: 
 dashboard.png  
 
 
Components: 
 github-organization-folder-plugin  
 
 
Created: 
 2017/Feb/06 9:00 AM  
 
 
Environment: 
 GitHub Organization Folder Plugin 1.5  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Vincent Massol  
 

  
 
 
 
 

 
 It's useful to be able to see at a glance failing jobs. It would be even nicer if the dashboard could be filtered for example to display only failed jobs. Right now the only info displayed is the weather but that's not enough to know if a job has failed or not. Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

   

[JIRA] (JENKINS-41664) Blue Ocean fails to load in MS Edge (Eventsource)

2017-02-06 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale assigned an issue to Tom FENNELLY  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41664  
 
 
  Blue Ocean fails to load in MS Edge (Eventsource)   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Assignee: 
 Tom FENNELLY  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41748) Environment variables cross references aren't supported

2017-02-06 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41748  
 
 
  Environment variables cross references aren't supported   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Andrew Bayer  
 
 
Components: 
 pipeline-model-definition-plugin  
 
 
Created: 
 2017/Feb/06 9:08 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Arnaud Héritier  
 

  
 
 
 
 

 
 Unlike documented here https://github.com/jenkinsci/pipeline-model-definition-plugin/wiki/Syntax-Reference such sample doesn't work 

 

environment {
FOO = "bar"
OTHER = "${FOO}baz"
}
 

 Firstly ${FOO} cannot work it is a groovy variable and it should be escaped 

 

OTHER = "\${FOO}baz"
 

 or  

 

OTHER = '${FOO}baz'
 

 And even by escaping it it's not working and we have 

 

[declarative-pipeline] Running shell script
+ printenv
...
OTHER=nullbaz
...
FOO=bar
...
 

 note that FOO is seen as null

[JIRA] (JENKINS-40978) Preview release of editor

2017-02-06 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale started work on  JENKINS-40978  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41349) Post-FOSDEM 2017 Hackathon

2017-02-06 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy assigned an issue to R. Tyler Croy  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41349  
 
 
  Post-FOSDEM 2017 Hackathon   
 

  
 
 
 
 

 
Change By: 
 R. Tyler Croy  
 
 
Assignee: 
 Kohsuke Kawaguchi R. Tyler Croy  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-40860) Go to the end of the expanded log

2017-02-06 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40860  
 
 
  Go to the end of the expanded log   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Sprint: 
 pannonian , panthalassa  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-40860) Go to the end of the expanded log

2017-02-06 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40860  
 
 
  Go to the end of the expanded log   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Sprint: 
 pannonian , iapetus  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-38523) Stage listing flashes "no steps" when loading a stage for the first time

2017-02-06 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38523  
 
 
  Stage listing flashes "no steps" when loading a stage for the first time   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Priority: 
 Major Critical  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41280) Hide organization prefix from UI

2017-02-06 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY started work on  JENKINS-41280  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Tom FENNELLY  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41748) Environment variables cross references aren't supported

2017-02-06 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier commented on  JENKINS-41748  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Environment variables cross references aren't supported   
 

  
 
 
 
 

 
 Environment : 

 

docker-workflow:1.9.1:not-pinned
pipeline-aggregator-view:1.4.1:not-pinned
pipeline-build-step:2.4:not-pinned
pipeline-github-lib:1.0:not-pinned
pipeline-graph-analysis:1.3:not-pinned
pipeline-input-step:2.5:not-pinned
pipeline-milestone-step:1.3:not-pinned
pipeline-model-api:1.0:not-pinned
pipeline-model-declarative-agent:1.0:not-pinned
pipeline-model-definition:1.0:not-pinned
pipeline-rest-api:2.4:not-pinned
pipeline-stage-step:2.2:not-pinned
pipeline-stage-tags-metadata:1.0:not-pinned
pipeline-stage-view:2.4:not-pinned
pipeline-utility-steps:1.2.2:not-pinned
workflow-aggregator:2.5:not-pinned
workflow-api:2.8:not-pinned
workflow-basic-steps:2.3:not-pinned
workflow-cps:2.25:not-pinned
workflow-cps-global-lib:2.5:not-pinned
workflow-durable-task-step:2.8:not-pinned
workflow-job:2.9:not-pinned
workflow-multibranch:2.12:not-pinned
workflow-scm-step:2.3:not-pinned
workflow-step-api:2.8:not-pinned
workflow-support:2.12:not-pinned
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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+unsubs

[JIRA] (JENKINS-41748) Environment variables cross references aren't supported

2017-02-06 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier edited a comment on  JENKINS-41748  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Environment variables cross references aren't supported   
 

  
 
 
 
 

 
 Environment :{code}docker-workflow:1.9.1:not-pinnedpipeline-aggregator-view:1.4.1:not-pinnedpipeline-build-step:2.4:not-pinnedpipeline-github-lib:1.0:not-pinnedpipeline-graph-analysis:1.3:not-pinnedpipeline-input-step:2.5:not-pinnedpipeline-milestone-step:1.3:not-pinnedpipeline-model-api:1.0:not-pinnedpipeline-model-declarative-agent:1.0:not-pinnedpipeline-model-definition:1.0:not-pinnedpipeline-rest-api:2.4:not-pinnedpipeline-stage-step:2.2:not-pinnedpipeline-stage-tags-metadata:1.0:not-pinnedpipeline-stage-view:2.4:not-pinnedpipeline-utility-steps:1.2.2:not-pinnedworkflow-aggregator:2.5:not-pinnedworkflow-api:2.8:not-pinnedworkflow-basic-steps:2.3:not-pinnedworkflow-cps:2.25:not-pinnedworkflow-cps-global-lib:2.5:not-pinnedworkflow-durable-task-step:2.8:not-pinnedworkflow-job:2.9:not-pinnedworkflow-multibranch:2.12:not-pinnedworkflow-scm-step:2.3:not-pinnedworkflow-step-api:2.8:not-pinnedworkflow-support:2.12:not-pinned{code} On Jenkins ver. 2.32.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41162) Input descriptions can contain html tags - allow or prevent

2017-02-06 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY updated  JENKINS-41162  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41162  
 
 
  Input descriptions can contain html tags - allow or prevent   
 

  
 
 
 
 

 
Change By: 
 Tom FENNELLY  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-39086) Scan Credentials dropdown is always empty

2017-02-06 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly commented on  JENKINS-39086  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Scan Credentials dropdown is always empty   
 

  
 
 
 
 

 
 The Add button cannot currently be provided with the context to know what credential types are accepted by the select drop down. Thus when you add credentials, there is nothing stopping you from adding an irrelevant type of credentials or even adding an irrelevant type into a credential domain that will not be matched. The best that we can do is to prevent the select drop down from allowing you to select invalid credentials  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-39086) Scan Credentials dropdown is always empty

2017-02-06 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly commented on  JENKINS-39086  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Scan Credentials dropdown is always empty   
 

  
 
 
 
 

 
 This is a duplicate of JENKINS-40293  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-39086) Scan Credentials dropdown is always empty

2017-02-06 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly closed an issue as Incomplete  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39086  
 
 
  Scan Credentials dropdown is always empty   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-40701) Add warning that Usage Tracking might not be exhaustive and depends on the consumer plugins

2017-02-06 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40701  
 
 
  Add warning that Usage Tracking might not be exhaustive and depends on the consumer plugins   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41489) Credentials add menu should not check only global permissions

2017-02-06 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41489  
 
 
  Credentials add menu should not check only global permissions   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-40914) Credentials plugin is not using the XSTREAM2 alias when opening the config file

2017-02-06 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40914  
 
 
  Credentials plugin is not using the XSTREAM2 alias when opening the config file   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-31683) p4-plugin out of memory with large depots on 32 bit java

2017-02-06 Thread heiko.nardm...@itechnical.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heiko Nardmann commented on  JENKINS-31683  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: p4-plugin out of memory with large depots on 32 bit java   
 

  
 
 
 
 

 
 Looks like I got that this morning, too: 

 
09:54:57 p4 reconcile -w -f -e -d D:\ci\workspace\some_job/...
09:54:57 
09:57:36 P4 Task: attempt: 1
09:57:39 P4 Task: failed: com.perforce.p4java.exception.ConnectionException: Java heap space
09:57:39 ERROR: P4 Task: failed: com.perforce.p4java.exception.ConnectionException: Java heap space
 

 I do not see a Java stack trace. Jenkins v2.21, P4 plugin v1.4.12. Jenkins runs on CentOS 7.2.1511 (64Bit). The slave system is Windows Server 2008 R2 Standard (64Bit). I'm not sure whether the Windows Java (jre1.8.0_121) is 32Bit or 64Bit. DependencyWalker says x86, so probably this is 32Bit.  Is 64Bit recommended? The failed job is a freestyle job. Acc. to /proc/.../maps the Java executable is  

 
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.111-2.6.7.2.el7_2.x86_64/jre-abrt/bin/java
 

 So this is the following package (see rpm -qif ...): 

 
Name: java-1.7.0-openjdk-headless
Epoch   : 1
Version : 1.7.0.111
Release : 2.6.7.2.el7_2
Architecture: x86_64
Install Date: Tue 15 Nov 2016 03:01:46 PM CET
Group   : Development/Languages
Size: 9015
License : ASL 1.1 and ASL 2.0 and GPL+ and GPLv2 and GPLv2 with exceptions and LGPL+ and LGPLv2 and MPLv1.0 and MPLv1.1 and Public Domain and W3C
Signature   : RSA/SHA256, Wed 27 Jul 2016 01:39:38 PM CEST, Key ID 24c6a8a7f4a80eb5
Source RPM  : java-1.7.0-openjdk-1.7.0.111-2.6.7.2.el7_2.src.rpm
Build Date  : Wed 27 Jul 2016 01:07:19 PM CEST
Build Host  : worker1.bsys.centos.org
Relocations : (not relocatable)
Packager: CentOS BuildSystem 
Vendor  : CentOS
URL : http://openjdk.java.net/
Summary : The OpenJDK runtime environment without audio and video support
Description :
The OpenJDK runtime environment without audio and video
 

  What is not clear to me: is this an issue on the server or on the slave agent? Ahh ... forget last question: acc. to slave agent error log: 

 
Feb 06, 2017 9:57:37 AM org.jenkinsci.plugins.p4.tasks.AbstractTask tryTask
SEVERE: P4 Task: attempt: 1
com.perforce.p4java.exception.ConnectionException: Java heap space
	at com.perforce.p4java.impl.mapbased.rpc.packet.RpcPacketDispatcher.dispatch(RpcPacketDispatcher.java:225)
	at com.perforce.p4java.impl.mapbased.rpc.OneShotServerImpl.execMapCmdList(OneShotServerImpl.java:350)
	at com.perforce.p4java.impl.mapbased.rpc.OneShotServerImpl.execStreamingMapCommand(OneShotServerImpl.java:415)
	at org.jenkinsci.plugins.p4.client.ClientHelper.tidyClean(ClientHelper.

[JIRA] (JENKINS-41749) Using regular expression to specify what jobs to include does not seem to work

2017-02-06 Thread per.oest...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Per Östman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41749  
 
 
  Using regular _expression_ to specify what jobs to include does not seem to work   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Paul Horvath  
 
 
Components: 
 pipeline-aggregator-view-plugin  
 
 
Created: 
 2017/Feb/06 9:45 AM  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Per Östman  
 

  
 
 
 
 

 
 When trying to use a regular _expression_ to select jobs to include in this view, no jobs are shown. E g a regular _expression_ of tsas., or ^tsas. yields empty list although it should not since there is a job named "tsas_multibranch_pipe".  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 


[JIRA] (JENKINS-38523) Stage listing flashes "no steps" when loading a stage for the first time (Karaoke repair)

2017-02-06 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38523  
 
 
  Stage listing flashes "no steps" when loading a stage for the first time (Karaoke repair)   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Summary: 
 Stage listing flashes "no steps" when loading a stage for the first time  (Karaoke repair)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41705) Unable to install bitbucket-branch-source 2.0.2 due to broken dependency

2017-02-06 Thread costescuand...@skymail.ro (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrei Costescu commented on  JENKINS-41705  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to install bitbucket-branch-source 2.0.2 due to broken dependency   
 

  
 
 
 
 

 
 Thanks. I will try that.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41750) commit status updating broken

2017-02-06 Thread fe...@debuggable.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Felix Geisendörfer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41750  
 
 
  commit status updating broken   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 github-branch-source-plugin  
 
 
Created: 
 2017/Feb/06 9:53 AM  
 
 
Environment: 
 System Properties   Name ↓  Value  awt.toolkit sun.awt.X11.XToolkit  executable-war /usr/lib/jenkins/jenkins.war  file.encoding UTF-8  file.encoding.pkg sun.io  file.separator /  guice.disable.misplaced.annotation.check true  java.awt.graphicsenv sun.awt.X11GraphicsEnvironment  java.awt.headless true  java.awt.printerjob sun.print.PSPrinterJob  java.class.path /usr/lib/jenkins/jenkins.war  java.class.version 51.0  java.endorsed.dirs /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.121.x86_64/jre/lib/endorsed  java.ext.dirs /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.121.x86_64/jre/lib/ext:/usr/java/packages/lib/ext  java.home /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.121.x86_64/jre  java.io.tmpdir /tmp  java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib  java.runtime.name OpenJDK Runtime Environment  java.runtime.version 1.7.0_121-mockbuild_2016_11_07_01_30-b00  java.specification.name Java Platform API Specification  java.specification.vendor Oracle Corporation  java.specification.version 1.7  java.vendor Oracle Corporation  java.vendor.url http://java.oracle.com/  java.vendor.url.bug http://bugreport.sun.com/bugreport/  java.version 1.7.0_121  java.vm.info mixed mode  java.vm.name OpenJDK 64-Bit Server VM  java.vm.specification.name Java Virtual Machine Specification  java.vm.specification.vendor Oracle Corporation  java.vm.specification.version 1.7  java.vm.vendor Oracle Corporation  java.vm.version 24.121-b00  javax.accessibility.assistive_technologies org.GNOME.Accessibility.JavaBridge  JENKINS_HOME /var/lib/jenkins  jna.loaded true  jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib:/usr/lib64/mysql  jnidispatch.path /tmp/jna--1712433994/jna7170532876831383862.tmp  line.separator  mail.smtp.sendpartial true  mail.smtps.sendpartial true  os.arch amd64  os.name Linux  os.version 4.1.12-61.1.25.el6uek.x86_64  path.separator :  sun.arch.data.model 64  sun.boot.class.path /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.121.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.121.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.121.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.121.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.121.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.121.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.121.x86_64/jre/lib/rhino.jar:/usr/lib/jvm/java-1.7.0-o

[JIRA] (JENKINS-41750) commit status updating broken

2017-02-06 Thread fe...@debuggable.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Felix Geisendörfer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41750  
 
 
  commit status updating broken   
 

  
 
 
 
 

 
Change By: 
 Felix Geisendörfer  
 

  
 
 
 
 

 
 As of today, the commit status updating of my multipipeline project stopped working, and I'm seeing the following error in the logs:{noformat}Could not update commit status.  Message  Message : {"message":"Not Found","documentation_url":"https://developer.github.com/enterprise/2.8/v3"}{noformat}The following changes were made since the last time things were working:* Upgraded all jenkins plugin (last update was ~2 weeks ago)* Re-created my scan credentials token as a "username/password" token since I'm unable to use my old "secret text" token since upgrading: see https://issues.jenkins-ci.org/browse/JENKINS-39086I think the token itself is okay. It has the 'repo:status' scope, and I've been able to manually create a commit status using the GH API via curl.Perhaps this is a recent regression causing the wrong HTTP request to be made for creating the commit status? Perhaps limited to GH Enterprise?I'm happy to provide more information, but I don't know how to get more debugging info on the actual http request that is causing the problem.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
   

[JIRA] (JENKINS-41750) commit status updating broken

2017-02-06 Thread fe...@debuggable.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Felix Geisendörfer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41750  
 
 
  commit status updating broken   
 

  
 
 
 
 

 
Change By: 
 Felix Geisendörfer  
 

  
 
 
 
 

 
 As of today, the commit status updating of my multipipeline project stopped working, and I'm seeing the following error in the logs:{noformat}Could not update commit status. Message: {"message":"Not Found","documentation_url":"https://developer.github.com/enterprise/2.8/v3"}{noformat}The following changes were made since the last time things were working:* Upgraded all jenkins plugin (last update was ~2 weeks ago)* Re-created my scan credentials token as a "username/password" token since I'm unable to use my old "secret text" token since upgrading: see https://issues.jenkins-ci.org/browse/JENKINS-39086I think the token itself is okay. It has the 'repo:status' scope, and I' ve been m  able to manually create a commit  status  statuses with it  using the GH API via curl.Perhaps this is a recent regression causing the wrong HTTP request to be made for creating the commit status? Perhaps limited to GH Enterprise?I'm happy to provide more information, but I don't know how to get more debugging info on the actual http request that is causing the problem.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
  

[JIRA] (JENKINS-41547) Container must have a max-width

2017-02-06 Thread jmcdon...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh McDonald commented on  JENKINS-41547  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Container must have a max-width   
 

  
 
 
 
 

 
 Fix is in https://github.com/jenkinsci/blueocean-plugin/pull/763  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41280) Hide organization prefix from UI

2017-02-06 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY commented on  JENKINS-41280  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Hide organization prefix from UI
 

  
 
 
 
 

 
 PR: https://github.com/jenkinsci/blueocean-plugin/pull/791  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41280) Hide organization prefix from UI

2017-02-06 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY updated  JENKINS-41280  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41280  
 
 
  Hide organization prefix from UI
 

  
 
 
 
 

 
Change By: 
 Tom FENNELLY  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41724) Cannot pull from bitbucket

2017-02-06 Thread dimakie...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dmytro Zhernosiekov closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Used git pull in "Build steps" without checkout. Fixed. Not a fault.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41724  
 
 
  Cannot pull from bitbucket   
 

  
 
 
 
 

 
Change By: 
 Dmytro Zhernosiekov  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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:/

[JIRA] (JENKINS-41370) Fix PCT for 2.32.1

2017-02-06 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-41370  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Fix PCT for 2.32.1   
 

  
 
 
 
 

 
 Code changed in jenkins User: Evaristo Gutiérrez Path: pom.xml src/main/java/com/cloudbees/hudson/plugins/folder/properties/FolderCredentialsProvider.java src/test/java/com/cloudbees/hudson/plugins/folder/FolderTest.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/c50a97de75b658f0b6199af16ccb8f3d7bdb4e6f Log: JENKINS-41370 Fix test which was failing for 2.32.1 version. Bump parent POM and jenkins test harness versions.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41370) Fix PCT for 2.32.1

2017-02-06 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-41370  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Fix PCT for 2.32.1   
 

  
 
 
 
 

 
 Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/com/cloudbees/hudson/plugins/folder/properties/FolderCredentialsProvider.java src/test/java/com/cloudbees/hudson/plugins/folder/FolderTest.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/304c051e6da33715d029f13a6570b439a2045082 Log: Merge pull request #84 from varyvol/JENKINS-41370 JENKINS-41370 Fix PCT for 2.32.1 Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/4e64cfcf7541...304c051e6da3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-40621) MavenEmbedderUtils#getMavenVersion() leaks file descriptors

2017-02-06 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier started work on  JENKINS-40621  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Arnaud Héritier  
 
 
Status: 
 Reopened In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-38736) update guice to release version

2017-02-06 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier started work on  JENKINS-38736  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Arnaud Héritier  
 
 
Status: 
 Reopened In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-36543) Boolean input parameter ignores default value of false

2017-02-06 Thread michael.dou...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Doubez commented on  JENKINS-36543  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Boolean input parameter ignores default value of false   
 

  
 
 
 
 

 
 Same issue in Jenkins 1.651.3. The API request seems good: 

 

{  "id":"Afdd284c9c42d46edfd421228b55be59",
   "proceedText":"Proceed",
   "message":"Boolean input test",
"inputs": [{"type":"BooleanParameterDefinition","name":"foo","definition":{"defaultVal":false}}],

 

 When looking at the HTML source, I see correct data: 

 

"input cbwf-info-action-popover run-input-required">
"remove">"glyphicon glyphicon-remove remove">
"caption">Boolean input test
"form">
"inputs">
"checkbox">

"foo" checked="false" type="checkbox">foo




"buttons">
"submit" class="btn btn-primary btn-sm proceed-button">Proceed
"submit" class="btn btn-default btn-sm abort-button">Abort




 

 But the dispaly is a checked box. The issue should be somewhere in the _javascript_ of pipeline-stage-view-plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
   

[JIRA] (JENKINS-36543) Boolean input parameter ignores default value of false

2017-02-06 Thread michael.dou...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Doubez edited a comment on  JENKINS-36543  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Boolean input parameter ignores default value of false   
 

  
 
 
 
 

 
 Same issue in Jenkins 1.651.3.The API request seems good:{code}{  "id":"Afdd284c9c42d46edfd421228b55be59",   "proceedText":"Proceed",   "message":"Boolean input test","inputs": [{"type":"BooleanParameterDefinition","name":"foo","definition":{"defaultVal":false}}],{code}When looking at the HTML source, I see correct data:{code}Boolean input test fooProceedAbort{code}But the  dispaly  display  is a checked box.The issue should be somewhere in the _javascript_ of pipeline-stage-view-plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41751) Groovy PowerAssertions don't show a useful message when being CPS transformed

2017-02-06 Thread martin.san...@sap.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Sander created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41751  
 
 
  Groovy PowerAssertions don't show a useful message when being CPS transformed   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline, workflow-cps-plugin  
 
 
Created: 
 2017/Feb/06 10:28 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Martin Sander  
 

  
 
 
 
 

 
 PowerAssertions are a really useful feature of the groovy programming language, as they give you the full information on what is not as it is expected in the error message - the full assert statement with all information about the values. However, when running CPS transformed, the output is less useful, as it only states what the assertion was that failed, without the values. Take for example the following pipeline script: 

 

node {
def a = 4
stage('without cps') {
nonCps(a)
}

stage('with cps') {
def b = [1, 2, 3]
try {
assert a == b[0]
} catch (Throwable e) {
echo e.class.toString()
echo e.message
echo e.stackTrace.join('\n')
}
}
}

@NonCPS
def nonCps(a) {
def b = [1, 2, 3]
try {
assert a == b[0]
} catch (Throwable e) {
echo e.class.toString()
echo e.message
echo e.stackTrace.join('\n')
}
}
 

 Although the code is the same for NonCPS and with CPS, NonCPS prints the following: 

 

assert a == b[0]
   ||
   |1
   false
 

  

[JIRA] (JENKINS-41370) Fix PCT for 2.32.1

2017-02-06 Thread egutier...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez updated  JENKINS-41370  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41370  
 
 
  Fix PCT for 2.32.1   
 

  
 
 
 
 

 
Change By: 
 Evaristo Gutierrez  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41752) Fix PCT for 2.32.2

2017-02-06 Thread egutier...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41752  
 
 
  Fix PCT for 2.32.2   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Evaristo Gutierrez  
 
 
Components: 
 credentials-binding-plugin  
 
 
Created: 
 2017/Feb/06 10:45 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Evaristo Gutierrez  
 

  
 
 
 
 

 
 Because of SECURITY-406, BindingStepTest#testGlobalBindingWithAuthorization is failing.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
   

[JIRA] (JENKINS-41752) Fix PCT for 2.32.2

2017-02-06 Thread egutier...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez started work on  JENKINS-41752  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Evaristo Gutierrez  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-31683) p4-plugin out of memory with large depots on 32 bit java

2017-02-06 Thread pal...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen commented on  JENKINS-31683  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: p4-plugin out of memory with large depots on 32 bit java   
 

  
 
 
 
 

 
 I wouldn't worry about Monday morning blindness - I have only just got back from a weeks skiing, so it will take me a while to get plugged back in. When you start the slave agent you can add arguments to the JVM -Xmx1024m (e.g. 1GB for the heap); this all depends on how you start the slave, the StackOverflow link discusses some of the options: http://stackoverflow.com/questions/5936519/how-to-give-jenkins-more-heap-space-when-it%C2%B4s-started-as-a-service-under-windows An alternative is to use the ForceClean option (it might be slower, but potentially uses less memory than reconcile).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41752) Fix PCT for 2.32.2

2017-02-06 Thread egutier...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez updated  JENKINS-41752  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41752  
 
 
  Fix PCT for 2.32.2   
 

  
 
 
 
 

 
Change By: 
 Evaristo Gutierrez  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41753) Rendering issue with

2017-02-06 Thread clecl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41753  
 
 
  Rendering issue with   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Sam Van Oort  
 
 
Attachments: 
 about.md, stage-view-gets-pushed-down-by-static-analysis-plugins.png  
 
 
Components: 
 pipeline-stage-view-plugin  
 
 
Created: 
 2017/Feb/06 10:53 AM  
 
 
Environment: 
  * CloudBees Jenkins Enterprise 2.32.2.1-rolling   * pipeline-stage-view:2.4 'Pipeline: Stage View Plugin'   * analysis-collector:1.50 'Static Analysis Collector Plug-in'   * analysis-core:1.82 'Static Analysis Utilities'  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Cyrille Le Clerc  
 

  
 
 
 
 

 
 Stage View get pushed down when the Static Code Analysis Plugin renders multiple diagrams (multiple static analysis tools, multi module project...) 
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
 

[JIRA] (JENKINS-41753) Rendering issue with Static Code Analysis Plugin

2017-02-06 Thread clecl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41753  
 
 
  Rendering issue with Static Code Analysis Plugin   
 

  
 
 
 
 

 
Change By: 
 Cyrille Le Clerc  
 
 
Summary: 
 Rendering issue with  Static Code Analysis Plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41753) Rendering issue with Static Code Analysis Plugin

2017-02-06 Thread clecl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41753  
 
 
  Rendering issue with Static Code Analysis Plugin   
 

  
 
 
 
 

 
Change By: 
 Cyrille Le Clerc  
 
 
Environment: 
  * CloudBees Jenkins Enterprise 2.32.2.1-rolling   * pipeline-stage-view:2.4 'Pipeline: Stage View Plugin'   * analysis-collector:1.50 'Static Analysis Collector Plug-in'   * analysis-core:1.82 'Static Analysis Utilities'  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41753) Rendering issue with Static Code Analysis Plugin

2017-02-06 Thread clecl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41753  
 
 
  Rendering issue with Static Code Analysis Plugin   
 

  
 
 
 
 

 
Change By: 
 Cyrille Le Clerc  
 
 
Environment: 
  * CloudBees Jenkins Enterprise 2.32.2.1-rolling   * pipeline-stage-view:2.4 'Pipeline: Stage View Plugin'   * analysis-collector:1.50 'Static Analysis Collector Plug-in'   * analysis-core:1.82 'Static Analysis Utilities'  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41754) thinBackup run custom script after backup

2017-02-06 Thread aleksey.kamen...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexey Kamenskiy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41754  
 
 
  thinBackup run custom script after backup   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Thomas Fürer  
 
 
Components: 
 thinbackup-plugin  
 
 
Created: 
 2017/Feb/06 10:56 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Alexey Kamenskiy  
 

  
 
 
 
 

 
 Feature idea: allow running custom scripts with this plugin after the backup is done. The script can be either Bash or Windows cmd depending on the environment. There are multiple requests that are covered by this feature: 
 
https://issues.jenkins-ci.org/browse/JENKINS-31548 
https://issues.jenkins-ci.org/browse/JENKINS-18757 
https://issues.jenkins-ci.org/browse/JENKINS-18353 
https://issues.jenkins-ci.org/browse/JENKINS-12125 
 Those are just few examples.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 


[JIRA] (JENKINS-36195) Pipeline polling ignores special polling rules

2017-02-06 Thread jukka.lehtni...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jukka Lehtniemi commented on  JENKINS-36195  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline polling ignores special polling rules   
 

  
 
 
 
 

 
 At least Included/Excluded regions actually works ok if you also specify Disable Remote Poll, e.g.: 

 

 checkout(
scm: [
extensions: [[$class: 'DisableRemotePoll'], [$class: 'PathRestriction', excludedRegions: '', includedRegions: 'foo/.*']]
])
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-36195) Pipeline polling ignores special polling rules

2017-02-06 Thread jukka.lehtni...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jukka Lehtniemi edited a comment on  JENKINS-36195  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline polling ignores special polling rules   
 

  
 
 
 
 

 
 At least _Included/Excluded regions_ actually works ok if you also specify _Disable Remote Poll_, e.g.:{code} checkout(  scm: [  ... , extensions: [[$class: 'DisableRemotePoll'], [$class: 'PathRestriction', excludedRegions: '', includedRegions: 'foo/.*']] , ... ]){code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-100) How to Launch a openstack windows instance from Jenkins

2017-02-06 Thread shimith.me...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shimith Menon created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 test /  TEST-100  
 
 
  How to Launch a openstack windows instance from Jenkins   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Components: 
 test1  
 
 
Created: 
 2017/Feb/06 11:24 AM  
 
 
Labels: 
 windows jenkins openstack  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Shimith Menon  
 

  
 
 
 
 

 
 Hi All, I have installed latest Jenkins for windows and I was trying to Integrate openstack windows images with Jenkins. For that I have installed all openstack Plugins and Now I can see an option "Openstack Instance Creation " ! Can anyone tell me the steps to add Cloud Name, template Name in that also Please let me know how that can be properly configured , so that I can launch a windows openstack instance from Jenkins. Any help is much appreciated.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

[JIRA] (JENKINS-41755) Background 'sh' invocation

2017-02-06 Thread k...@kohsuke.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kohsuke Kawaguchi created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41755  
 
 
  Background 'sh' invocation   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Components: 
 workflow-durable-task-step-plugin  
 
 
Created: 
 2017/Feb/06 11:30 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Kohsuke Kawaguchi  
 

  
 
 
 
 

 
 In an attempt to make Android emulator plugin pipeline-enabled, Christopher Orr and I felt it would be nice if the sh step supports background task invocation. That is, {{sh} step returns immediately with some object that represents the process, with some methods on it to interact with it. This would be used to run Android emulator in the background in such a way that its lifespan is tied to a pipeline build and not affected by a loss of master/agent/communication.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  

[JIRA] (JENKINS-41755) Background 'sh' invocation

2017-02-06 Thread k...@kohsuke.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kohsuke Kawaguchi commented on  JENKINS-41755  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Background 'sh' invocation   
 

  
 
 
 
 

 
 Posted the PR  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41756) Indecently translated main menu items

2017-02-06 Thread umali...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Uroš Malenšek created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41756  
 
 
  Indecently translated main menu items   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Attachments: 
 jenkins1.png, jenkins2.png  
 
 
Components: 
 _unsorted  
 
 
Created: 
 2017/Feb/06 11:47 AM  
 
 
Environment: 
 I am running docker image of Jenkins version 2.32.2.  Using Firefox 51.0.1 (32-bit)
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Uroš Malenšek  
 

  
 
 
 
 

 
 In main menu I have noted two items indicently translated to slovene. See attachments. Item "With my ass" opens page "Project Relationship" Item "Otisci guza" opens page "Check File Fingerprints". This one is not slovene translation but means "Ass prints" in croatian. There may be some other failures as well that I missed. I do not know where these could be easily fixed. As it stands now it is not production ready.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment 

[JIRA] (JENKINS-41689) Unable to download S3 artifact from link

2017-02-06 Thread jacopo.sabbat...@polymathian.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacopo Sabbatini commented on  JENKINS-41689  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to download S3 artifact from link   
 

  
 
 
 
 

 
 Setting the system did it thanks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41689) Unable to download S3 artifact from link

2017-02-06 Thread jacopo.sabbat...@polymathian.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacopo Sabbatini closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41689  
 
 
  Unable to download S3 artifact from link   
 

  
 
 
 
 

 
Change By: 
 Jacopo Sabbatini  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


  1   2   3   4   5   >