[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title trinadh teegala assigned an issue to Paul Weber Jenkins / JENKINS-59542 There is problem while I'm trying to give CIFS share builds in Jenkins Change By: trinadh teegala Assignee: Paul Weber Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202172.1569500879000.846.1570167540292%40Atlassian.JIRA.
[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title trinadh teegala commented on JENKINS-59542 Re: There is problem while I'm trying to give CIFS share builds in Jenkins Hi Paul, Can you please let me know who can help me on this issue Thanks Trinadh Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202172.1569500879000.848.1570167540327%40Atlassian.JIRA.
[JIRA] (JENKINS-59650) Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻
Title: Message Title Jesse Houghton edited a comment on JENKINS-59650 Re: Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻ Hi [~mhall4] I believe this has been fixed as of weekly release 2.196 - It looks like it's marked for back porting in 2.190.2 (The next version of the LTS version) I've added a link this Jira to the previous issue. Here's results from a local test on the latest code stream:!image-2019-10-04-18-11-04-221.png! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202340.1570126979000.843.1570165920174%40Atlassian.JIRA.
[JIRA] (JENKINS-59650) Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻
Title: Message Title Jesse Houghton commented on JENKINS-59650 Re: Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻ Hi Matthew Hall I believe this has been fixed as of weekly release 2.196 - It looks like it's marked for back porting in 2.190.2 (The next version of the LTS version) I've added a link this Jira to the previous issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202340.1570126979000.841.1570165860158%40Atlassian.JIRA.
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Morgan Robertson commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost We see this with GitHub, multi-branch pipelines & Jenkins version 2.193. Happy to provide any further details to assist in narrowing it down. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196298.154504211.836.1570158120627%40Atlassian.JIRA.
[JIRA] (JENKINS-57381) Entire Build History for project is removed and Build number is reset
Title: Message Title Morgan Robertson commented on JENKINS-57381 Re: Entire Build History for project is removed and Build number is reset This is very similar to https://issues.jenkins-ci.org/browse/JENKINS-55220 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199162.1557377445000.839.1570158120670%40Atlassian.JIRA.
[JIRA] (JENKINS-59651) PIPELINE_VERSION can not export to shell environment.
Title: Message Title Alex Lei updated an issue Jenkins / JENKINS-59651 PIPELINE_VERSION can not export to shell environment. Change By: Alex Lei Then plugin works file when I use old jenkins release. when When I upgrade jenkins to latest version. I found shel shell env missing PIPELINE_VERSION variable. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202341.1570157505000.825.1570157880187%40Atlassian.JIRA.
[JIRA] (JENKINS-59651) PIPELINE_VERSION can not export to shell environment.
Title: Message Title Alex Lei updated an issue Jenkins / JENKINS-59651 PIPELINE_VERSION can not export to shell environment. Change By: Alex Lei Summary: PIPELINE_VERSION can note not export to shell environment. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202341.1570157505000.823.1570157580262%40Atlassian.JIRA.
[JIRA] (JENKINS-59651) PIPELINE_VERSION can note export to shell environment.
Title: Message Title Alex Lei created an issue Jenkins / JENKINS-59651 PIPELINE_VERSION can note export to shell environment. Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 2019-10-04 02:51 Environment: jenkins-2.187.war osx jdk8 Priority: Critical Reporter: Alex Lei Then plugin works file when I use old jenkins release. when I upgrade jenkins to latest version. I found shel env missing PIPELINE_VERSION variable. Add Comment
[JIRA] (JENKINS-50772) Content type not set reasonably
Title: Message Title Robin Verduijn commented on JENKINS-50772 Re: Content type not set reasonably I took a stab at this, and was able to get a custom-built version of the plugin working for me locally: it uploads files to S3 with content-type set appropriately which makes them properly viewable in the browser (for inline file types such as text/plain and text/html) instead of always forcing them to be downloaded. This took changes to both the artifact-manager-s3 and apache-httpcomponents-client-4-api-plugin repositories, since I had to ensure when the plugin performs an HTTP upload it also specifies the "Content-Type" header and I used a new method signature in RobustHTTPClient to do so. My changes can be viewed at: https://github.com/jenkinsci/apache-httpcomponents-client-4-api-plugin/pull/24 https://github.com/jenkinsci/artifact-manager-s3-plugin/pull/100 While, as I said, a custom plugin that has these changes appears to do the right thing for me and I also added several tests to verify uploads to (and subsequent downloads from) S3 are setting the content-type now, this is my first contribution to the project so I might well have missed something. Any suggestions or feedback welcome... I hope it at least provides a starting point for a fix to this issue, if nothing else. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are
[JIRA] (JENKINS-56468) githubPRComment throws NPE
Title: Message Title Scott Hubbard commented on JENKINS-56468 Re: githubPRComment throws NPE I am running the plugin version 2.5.8 on Jenkins 2.197 and I see the same exception. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198067.1551981547000.810.1570145580214%40Atlassian.JIRA.
[JIRA] (JENKINS-48518) Docker Pipeline: invalid volume specification with Windows slave and Linux master
Title: Message Title a b edited a comment on JENKINS-48518 Re: Docker Pipeline: invalid volume specification with Windows slave and Linux master We are also running into the same issue and can confirm that removing the ",z" portion resolves the "invalid volume specification" errorRunning Windows Server 2016 with Docker 19.03.2, build c92ab06ed9 (CLI only not the Docker Desktop app).How can we go about resolving this issue for nodes with a Windows host OS? I love and much prefer Linux but sadly we have developer requirements on the Windows side and have to support it in our pipelines. *EDIT*: I'm going to assume this concept is dead in the water based on this thread.. I have browsed through the source and it's riddled with Linux specific commands for interacting with docker and there seems to be zero appetite for making it Windows compatible.https://issues.jenkins-ci.org/browse/JENKINS-36776We are going to attempt to use the alternate docker-plugin which interacts directly with the Docker Engine API on the host and thus should be more host OS agnostic, though there might be more quirks there too. TBD. The immediate downside is there doesn't seem to be support for Dockerfile files and the images have be be pre-build and pre-defined in the plugin UI under Configure > Cloud > Docker which is odd and kind of ridiculous since this moves away from CI/CD philosophies I'd argue and move programmable features into a UI. Sad. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-59648) UX improvements
Title: Message Title Arnaud Héritier commented on JENKINS-59648 Re: UX improvements Screenshots with 2.138.4 cc Ryan Campbell / Parker Ennis Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202338.1570118477000.794.1570141860157%40Atlassian.JIRA.
[JIRA] (JENKINS-59648) UX improvements
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59648 UX improvements Change By: Arnaud Héritier Attachment: Screenshot 2019-10-04 00.28.09.png Attachment: Screenshot 2019-10-04 00.27.47.png Attachment: Screenshot 2019-10-04 00.25.18.png Attachment: Screenshot 2019-10-04 00.24.58.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Arnaud Héritier updated JENKINS-59644 Jenkins / JENKINS-59644 Upgrade Jenkins core pre-requisite to 2.138.4 Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202334.1570111402000.792.1570141260259%40Atlassian.JIRA.
[JIRA] (JENKINS-59648) UX improvements
Title: Message Title Arnaud Héritier commented on JENKINS-59648 Re: UX improvements PR: https://github.com/jenkinsci/cloudbees-jenkins-advisor-plugin/pull/37 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202338.1570118477000.789.1570141200111%40Atlassian.JIRA.
[JIRA] (JENKINS-59648) UX improvements
Title: Message Title Arnaud Héritier updated JENKINS-59648 Jenkins / JENKINS-59648 UX improvements Change By: Arnaud Héritier Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202338.1570118477000.790.1570141200173%40Atlassian.JIRA.
[JIRA] (JENKINS-59648) UX improvements
Title: Message Title Arnaud Héritier commented on JENKINS-59648 Re: UX improvements UI Before: UI After: Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202338.1570118477000.788.1570141080094%40Atlassian.JIRA.
[JIRA] (JENKINS-59648) UX improvements
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59648 UX improvements Change By: Arnaud Héritier Attachment: Screenshot 2019-10-04 00.15.07.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202338.1570118477000.786.1570140960103%40Atlassian.JIRA.
[JIRA] (JENKINS-59648) UX improvements
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59648 UX improvements Change By: Arnaud Héritier Attachment: Screenshot 2019-10-04 00.11.13.png Attachment: Screenshot 2019-10-04 00.09.30.png Attachment: Screenshot 2019-10-04 00.09.11.png Attachment: Screenshot 2019-10-04 00.08.53.png Attachment: Screenshot 2019-10-04 00.08.34.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59648) UX improvements
Title: Message Title Arnaud Héritier commented on JENKINS-59648 Re: UX improvements example of logs with the change : Oct 03, 2019 6:59:12 PM hudson.model.AsyncPeriodicWork$1 run INFO: Started Bundle Upload Oct 03, 2019 6:59:12 PM com.cloudbees.jenkins.plugins.advisor.BundleUpload log INFO: User not registered. Skipping bundle upload. Oct 03, 2019 6:59:12 PM hudson.model.AsyncPeriodicWork$1 run INFO: Finished Bundle Upload. 1 ms ^^ The message will be updated (there is no notion of users registration today) or Oct 03, 2019 7:05:29 PM hudson.model.AsyncPeriodicWork$1 run INFO: Started Bundle Upload Oct 03, 2019 7:05:29 PM com.cloudbees.jenkins.plugins.advisor.BundleUpload log INFO: User not registered. Skipping bundle upload. Oct 03, 2019 7:05:29 PM hudson.model.AsyncPeriodicWork$1 run INFO: Finished Bundle Upload. 1 ms Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-59650) Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻
Title: Message Title
Matthew Hall edited a comment on JENKINS-59650
Re: Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻
Also, to use another example. If I create :{noformat}See No Evil :see no evil monkey: {noformat}as a job, this works.If I try to create it as :{noformat}:see no evil monkey: See No Evil{noformat}It fails. Seems to be related to the emoji being the leading part of the job name. (I can't use the actual monkey, due to Jira not taking it : It fails.][numvalue,null][updated,2019-10-03 18:41:35.326] (SQL Exception while executing the following:UPDATE jiraaction SET issueid=?, AUTHOR=?, actiontype=?, actionlevel=?, rolelevel=?, actionbody=?, CREATED=?, UPDATEAUTHOR=?, UPDATED=?, actionnum=? WHERE ID=? (Incorrect string value: '\xF0\x9F\x99\x88: ...' for column 'actionbody' at row 1)))
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202340.1570126979000.766.1570128840055%40Atlassian.JIRA.
[JIRA] (JENKINS-59650) Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻
Title: Message Title Matthew Hall updated an issue Jenkins / JENKINS-59650 Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻ Change By: Matthew Hall Labels: emoji Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202340.1570126979000.765.1570128720067%40Atlassian.JIRA.
[JIRA] (JENKINS-59650) Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻
Title: Message Title
Matthew Hall edited a comment on JENKINS-59650
Re: Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻
Also, to use another example. If I create :{noformat}See No Evil :see no evil monkey: {noformat}as a job, this works.If I try to create it as :{noformat}:see no evil monkey: See No Evil{noformat}It fails. (I can't use the actual monkey, due to Jira not taking it : It fails.][numvalue,null][updated,2019-10-03 18:41:35.326] (SQL Exception while executing the following:UPDATE jiraaction SET issueid=?, AUTHOR=?, actiontype=?, actionlevel=?, rolelevel=?, actionbody=?, CREATED=?, UPDATEAUTHOR=?, UPDATED=?, actionnum=? WHERE ID=? (Incorrect string value: '\xF0\x9F\x99\x88: ...' for column 'actionbody' at row 1)))
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202340.1570126979000.764.1570128180060%40Atlassian.JIRA.
[JIRA] (JENKINS-59650) Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻
Title: Message Title Matthew Hall commented on JENKINS-59650 Re: Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻ Also, to use another example. If I create : See No Evil :see no evil monkey: as a job, this works. If I try to create it as : :see no evil monkey: See No Evil It fails. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202340.1570126979000.763.1570128120051%40Atlassian.JIRA.
[JIRA] (JENKINS-59650) Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻
Title: Message Title
Matthew Hall edited a comment on JENKINS-59650
Re: Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻
{noformat} [root@jmtest jobs]# cd \ (╯°□° \ )╯︵\ ┻━┻/[root@jmtest (╯°□°)╯︵ ┻━┻]# lsbuilds config.xml[root@jmtest (╯°□°)╯︵ ┻━┻]# ls -altotal 32drwxr-xr-x 3 jenkins jenkins 4096 Oct 3 11:19 .drwxr-xr-x 405 jenkins jenkins 20480 Oct 3 11:19 ..drwxr-xr-x 2 jenkins jenkins 4096 Oct 3 11:19 builds - rw- r rr - -r-- 1 jenkins jenkins 206 Oct 3 11:19 config.xml[root@jmtest (╯°□°)╯︵ ┻━┻]# more config.xml false false[root@jmtest (╯°□°)╯︵ ┻━┻]# ls buildslegacyIds[root@jmtest (╯°□°)╯︵ ┻━┻]# pwd/home/jenkins/jobs/(╯°□°)╯︵ ┻━┻ {noformat}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202340.1570126979000.762.1570127340070%40Atlassian.JIRA.
[JIRA] (JENKINS-59650) Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻
Title: Message Title
Matthew Hall edited a comment on JENKINS-59650
Re: Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻
{{ [root@jmtest jobs]# cd \(╯°□°\)╯︵\ ┻━┻/[root@jmtest (╯°□°)╯︵ ┻━┻]# lsbuilds config.xml[root@jmtest (╯°□°)╯︵ ┻━┻]# ls -altotal 32drwxr-xr-x 3 jenkins jenkins 4096 Oct 3 11:19 .drwxr-xr-x 405 jenkins jenkins 20480 Oct 3 11:19 ..drwxr-xr-x 2 jenkins jenkins 4096 Oct 3 11:19 builds-rw-r--r-- 1 jenkins jenkins 206 Oct 3 11:19 config.xml[root@jmtest (╯°□°)╯︵ ┻━┻]# more config.xml false false[root@jmtest (╯°□°)╯︵ ┻━┻]# ls buildslegacyIds[root@jmtest (╯°□°)╯︵ ┻━┻]# pwd/home/jenkins/jobs/(╯°□°)╯︵ ┻━┻ }}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202340.1570126979000.761.1570127280056%40Atlassian.JIRA.
[JIRA] (JENKINS-59650) Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻
Title: Message Title
Matthew Hall commented on JENKINS-59650
Re: Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻
{{[root@jmtest jobs]# cd (╯°□°)╯︵\ ┻━┻/ [root@jmtest (╯°□°)╯︵ ┻━┻]# ls builds config.xml [root@jmtest (╯°□°)╯︵ ┻━┻]# ls -al total 32 drwxr-xr-x 3 jenkins jenkins 4096 Oct 3 11:19 . drwxr-xr-x 405 jenkins jenkins 20480 Oct 3 11:19 .. drwxr-xr-x 2 jenkins jenkins 4096 Oct 3 11:19 builds rw-rr- 1 jenkins jenkins 206 Oct 3 11:19 config.xml [root@jmtest (╯°□°)╯︵ ┻━┻]# more config.xmlfalse false [root@jmtest (╯°□°)╯︵ ┻━┻]# ls builds legacyIds [root@jmtest (╯°□°)╯︵ ┻━┻]# pwd /home/jenkins/jobs/(╯°□°)╯︵ ┻━┻}}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202340.1570126979000.760.1570127220062%40Atlassian.JIRA.
[JIRA] (JENKINS-59650) Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻
Title: Message Title Matthew Hall updated an issue Jenkins / JENKINS-59650 Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻ Change By: Matthew Hall Attachment: stacktrace.log Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202340.1570126979000.759.1570127100141%40Atlassian.JIRA.
[JIRA] (JENKINS-59650) Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻
Title: Message Title Matthew Hall created an issue Jenkins / JENKINS-59650 Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻ Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-10-03 18:22 Environment: Jenkins 2.190.1 Priority: Minor Reporter: Matthew Hall Tried to create job named "(╯°□°)╯︵ ┻━┻" Expected results : Would move to job configuration page. Actual results : (java stack trace) Now, if I create a similar job, but I use some leading ascii text, eg: Tried to create job named : "TBF (╯°□°)╯︵ ┻━┻" Expected results : Would move to job configuration page. Actual results : Moved to job configuration page. If I inspect the JENKINS_HOME/jobs directory, the (╯°□°)╯︵ ┻━┻ directory does get created, but I am unable to configure this through the GUI. Add Comment
[JIRA] (JENKINS-59649) Inter-pod and external communication
Title: Message Title Peter Jonsson created an issue Jenkins / JENKINS-59649 Inter-pod and external communication Issue Type: New Feature Assignee: Unassigned Components: kubernetes-plugin Created: 2019-10-03 17:17 Priority: Minor Reporter: Peter Jonsson Sometimes, it is not always possible to put everything inside the same Kubernetes pod - or inside a container at all. Any of the following reasons can make it troublesome: Already existing tooling. Licensing that is not adapted to containerization or that outright does not allow containerization. Operating systems that cannot be containerized (i.e. macOS). Purchased and packaged solutions. Legacy systems that are either infeasible to port or too expensive to make it viable. I am sure that there are even more reasons. A concrete example is to use Selenium from a Windows-based agent that does not reside within the Kubernetes cluster to execute tests on a server that is deployed to Kubernetes using the plugin. How would the non-container Selenium instance know where a website is hosted within the Kubernetes pod? Thus, there is a use case for interfacing with Kubernetes containers/pods from outside the pod, in which case other containers can no longer be interacted with using `localhost`. In order to use the Kubernetes plugin with other external (i.e. outside of the pod) Jenkins agents there must be a way of addressing the specific pod through either an IP-address or some "magic" DNS-alias. Preferably, this should work within a declarative pipeline as a scripted pipeline could read the IP from the containers
[JIRA] (JENKINS-59645) Encoding problems after update to version 2.190.1
Title: Message Title Jonathan Gonçalves updated an issue Jenkins / JENKINS-59645 Encoding problems after update to version 2.190.1 Change By: Jonathan Gonçalves After update from 2.176.1 to 2.190.1 some projects with accents can't be access anymore because the Job link appears empty. Another problem is in Blueocean, that doesnt show project names with accents.Another problem is in the job execution, that throw an Exception when try to build projects with accents on name. EDIT: Tested same things on 2.176.4 version and none of these errors occours. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202335.1570113234000.753.1570122000322%40Atlassian.JIRA.
[JIRA] (JENKINS-58727) Misleading log message when no e-mail is sent
Title: Message Title Richard Lee commented on JENKINS-58727 Re: Misleading log message when no e-mail is sent Please fix this. It makes it appear that the build notification system is broken, when in fact it is not. Causes a lot of unnecessary worry. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201021.1564483585000.749.1570121760200%40Atlassian.JIRA.
[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title Alex Earl commented on JENKINS-59542 Re: There is problem while I'm trying to give CIFS share builds in Jenkins Stop assigning this to me. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202172.1569500879000.744.1570119360142%40Atlassian.JIRA.
[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title Alex Earl assigned an issue to Unassigned Jenkins / JENKINS-59542 There is problem while I'm trying to give CIFS share builds in Jenkins Change By: Alex Earl Assignee: Alex Earl Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202172.1569500879000.742.1570119300658%40Atlassian.JIRA.
[JIRA] (JENKINS-59613) Rename the plugin "Jenkins Health Advisor by CloudBees"
Title: Message Title Arnaud Héritier updated JENKINS-59613 Jenkins / JENKINS-59613 Rename the plugin "Jenkins Health Advisor by CloudBees" Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Released As: cloudbees-jenkins-advisor-2.11 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202254.1569951438000.729.1570118820239%40Atlassian.JIRA.
[JIRA] (JENKINS-59618) Upgrade parent pom + configure plugin metadata
Title: Message Title Arnaud Héritier updated JENKINS-59618 Jenkins / JENKINS-59618 Upgrade parent pom + configure plugin metadata Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Released As: cloudbees-jenkins-advisor-2.11 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202259.1569961496000.731.1570118826517%40Atlassian.JIRA.
[JIRA] (JENKINS-59614) New icon for Jenkins Health Advisor by CloudBees
Title: Message Title Arnaud Héritier updated JENKINS-59614 Jenkins / JENKINS-59614 New icon for Jenkins Health Advisor by CloudBees Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Released As: cloudbees-jenkins-advisor-2.11 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202255.156995264.730.1570118826483%40Atlassian.JIRA.
[JIRA] (JENKINS-59648) UX improvements
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59648 UX improvements Issue Type: Task Assignee: Arnaud Héritier Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-03 16:01 Priority: Major Reporter: Arnaud Héritier While testing the plugin I found various small improvements to do to improve a bit the user experience: Logs are showing that the upload task is starting/finishing while it does nothing (because TOS aren't accepted for example). It's confusing and could let think that an upload happens which isn't the case Oct 03, 2019 3:17:55 PM hudson.model.AsyncPeriodicWork$1 run INFO: Started Bundle Upload Oct 03, 2019 3:17:55 PM hudson.model.AsyncPeriodicWork$1 run INFO: Finished Bundle Upload. 1 ms The configuration screen could be improved a bit by just reordering some fields (it's confusing to accept the TOS at the bottom of the form while it it is the most important setting. Without accepting the TOS nothing happens) Few messages / sentences could be improved
[JIRA] (JENKINS-59648) UX improvements
Title: Message Title Arnaud Héritier started work on JENKINS-59648 Change By: Arnaud Héritier Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202338.1570118477000.728.1570118520200%40Atlassian.JIRA.
[JIRA] (JENKINS-59647) Upgrade support-core dependency to 2.62
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59647 Upgrade support-core dependency to 2.62 Issue Type: Task Assignee: Arnaud Héritier Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-03 15:54 Priority: Major Reporter: Arnaud Héritier 2.62 isn't yet released but it should be soon by Evaristo Gutierrez 2.62 has also 2.138.4 as core requirement ( we are upgrading with JENKINS-59644 ) We are now depending of 2.44 which was released in dec 2017. Recent versions of support-core are providing a lot of improvements (like anonymisation), are grabbing new details useful for some probes. FYI Ryan Campbell I suppose you're ok Owen Wood ? Add Comment
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Arnaud Héritier commented on JENKINS-59644 Re: Upgrade Jenkins core pre-requisite to 2.138.4 PR: https://github.com/jenkinsci/cloudbees-jenkins-advisor-plugin/pull/36 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202334.1570111402000.721.1570117440919%40Atlassian.JIRA.
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Arnaud Héritier started work on JENKINS-59644 Change By: Arnaud Héritier Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202334.1570111402000.722.1570117441062%40Atlassian.JIRA.
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Arnaud Héritier updated JENKINS-59644 Jenkins / JENKINS-59644 Upgrade Jenkins core pre-requisite to 2.138.4 Change By: Arnaud Héritier Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202334.1570111402000.724.1570117441432%40Atlassian.JIRA.
[JIRA] (JENKINS-42825) input steps should be able to automatically popup a dialogue box in the stage view
Title: Message Title Jim D commented on JENKINS-42825 Re: input steps should be able to automatically popup a dialogue box in the stage view This definitely helps the case where the user has clicked on the job page and a build is waiting for input. Each time I explain to job users that they must hover, it takes a while for them to get used to it. And it also helps the case where the user has opened the popup by hovering and there are inputs to fill out like strings or choices, since the popup is so small and constantly users are letting their mouse pointer drift, which kills the popup in the middle of editing the input form. I've seen our users try to fill out a popup over and over again unsuccessfully, and finally have to show them there's a way to get to the plain HTML "Paused for input" form page instead. Even if the popup weren't automatic when the job page is rendered, if there were a way to open it besides the hover, it would improve usability. An explicit link or button inside the "paused" stage cell would be more obvious, and it wouldn't require a delay before showing the popup, and since the user actually clicked, presumably the popup could just stay open. (Note that I don't know why the popup has an "X" close button either, since it disappears so easily when you move the mouse. This might make the "X" close button be more useful too.) The version we're using currently is: org.jenkins-ci.plugins.pipeline-stage-view:pipeline-stage-view:2.12 Jenkins 2.176.3 Firefox 68.0.2esr Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Arnaud Héritier commented on JENKINS-59644 Re: Upgrade Jenkins core pre-requisite to 2.138.4 We can remove the code related to the support of jenkins core < 2.103 ( JENKINS-43786 ) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202334.1570111402000.719.1570117260332%40Atlassian.JIRA.
[JIRA] (JENKINS-59622) Sparse checkout definition change not applied to workspace
Title: Message Title Mark Waite commented on JENKINS-59622 Re: Sparse checkout definition change not applied to workspace The git plugin does not apply changes to the sparse checkout definition to the workspace. A workaround in Pipeline is to use deleteDir() in the Jenkinsfile when making this type of structural change. The workspace will be removed by the call to deleteDir() and then the currently defined sparse checkout will be applied to the fresh checkout. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202266.1570009158000.715.1570116900167%40Atlassian.JIRA.
[JIRA] (JENKINS-59622) Sparse checkout definition change not applied to workspace
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59622 Sparse checkout definition change not applied to workspace Change By: Mark Waite Summary: Jenkins workspace can Sparse checkout definition change not be updated automatically applied to workspace Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202266.1570009158000.711.1570116780327%40Atlassian.JIRA.
[JIRA] (JENKINS-59622) Jenkins workspace can not be updated automatically
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59622 Jenkins workspace can not be updated automatically Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202266.1570009158000.709.1570116780262%40Atlassian.JIRA.
[JIRA] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title Mark Waite commented on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) Jai Mishra no fix has been implemented. Cenk Tosun reported a workaround in an earlier comment. Are you absolutely certain after reading all the descriptions and comments that your issue is the same problem as described here? If so, does the workaround from Cenk Tosun also fix it for you? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192737.1533040103000.699.1570116240475%40Atlassian.JIRA.
[JIRA] (JENKINS-58949) If job fails in cleanup further triggering fails
Title: Message Title Karl Wirth commented on JENKINS-58949 Re: If job fails in cleanup further triggering fails Tested and bug still seen. Additional changes going in at the moment so retest in 1 week. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201296.1565876577000.696.1570116120112%40Atlassian.JIRA.
[JIRA] (JENKINS-59646) Migrate badge plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-59646 Migrate badge plugin documentation from Wiki to GitHub Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202336.1570115224000.692.1570115640088%40Atlassian.JIRA.
[JIRA] (JENKINS-59646) Migrate badge plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite started work on JENKINS-59646 Change By: Mark Waite Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202336.1570115224000.690.1570115460248%40Atlassian.JIRA.
[JIRA] (JENKINS-59646) Migrate badge plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite updated JENKINS-59646 Jenkins / JENKINS-59646 Migrate badge plugin documentation from Wiki to GitHub Change By: Mark Waite Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202336.1570115224000.691.1570115460293%40Atlassian.JIRA.
[JIRA] (JENKINS-59646) Migrate badge plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-59646 Migrate badge plugin documentation from Wiki to GitHub Issue Type: Improvement Assignee: Unassigned Components: other Created: 2019-10-03 15:07 Labels: hacktoberfest newbie-friendly Priority: Minor Reporter: Mark Waite We have recently introduced support of GitHub documentation on the Jenkins Plugin Site. See https://groups.google.com/forum/#!topic/jenkinsci-dev/VSdfVMDIW-A for the announcement. Jenkins users seeking documentation will have a better user experience on plugins.jenkins.io than they do on wiki.jenkins.io. At the same time, maintainers can follow the documentation-as-code approach and make documentation changes a part of pull requests. Documentation changes will be reviewed as part of pull requests and documentation contributors will be recognized, especially when combined with Release Drafter. We recommend all plugins to migrate documentation to GitHub. Steps: Select a plugin you want to improve, clone this issue and assign the correct component ID Review the plugin page on the Wiki and in the GitHub README. If there is missing information in the README, submit a pull request with the documentation update Modify the documentation URL in the project file: https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Referencingthedocumentationpagefromtheprojectfile Once the steps are completed and your pull request is merged by the maintainer, the GitHub landing page will be
[JIRA] (JENKINS-29166) Repository Connector Plugin doesn't refresh the list of artifacts stored on maven repository
Title: Message Title Julien Béti commented on JENKINS-29166 Re: Repository Connector Plugin doesn't refresh the list of artifacts stored on maven repository I have version 1.2.6, and I have the issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163627.1435755906000.681.1570115281050%40Atlassian.JIRA.
[JIRA] (JENKINS-59646) Migrate badge plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59646 Migrate badge plugin documentation from Wiki to GitHub Change By: Mark Waite We have recently introduced support of GitHub documentation on the [Jenkins Plugin Site|https://plugins.jenkins.io/]. See [https://groups.google.com/forum/#!topic/jenkinsci-dev/VSdfVMDIW-A] for the announcement. Jenkins users seeking documentation will have a better user experience on plugins.jenkins.io than they do on wiki.jenkins.io. At the same time, maintainers can follow the documentation-as-code approach and make documentation changes a part of pull requests. Documentation changes will be reviewed as part of pull requests and documentation contributors will be recognized, especially when combined with [Release Drafter|https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.adoc]. We recommend all plugins to migrate documentation to GitHub.Steps: * Select a plugin you want to improve (badge-plugin) , clone this issue and assign the correct component ID * Review the plugin page on the Wiki and in the GitHub README. If there is missing information in the README, submit a pull request with the documentation update * Modify the documentation URL in the project file: [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Referencingthedocumentationpagefromtheprojectfile]Once the steps are completed and your pull request is merged by the maintainer, the GitHub landing page will be updated. The next time the plugin releases, the documentation will appear on https://plugins.jenkins.io/. Add Comment
[JIRA] (JENKINS-30267) Maven repository artifact does not showing newly updated version from Nexus Maven Repository
Title: Message Title Julien Béti commented on JENKINS-30267 Re: Maven repository artifact does not showing newly updated version from Nexus Maven Repository I have version 1.2.6, and I have the issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164854.1441201253000.688.1570115281142%40Atlassian.JIRA.
[JIRA] (JENKINS-59646) Migrate badge plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59646 Migrate badge plugin documentation from Wiki to GitHub Change By: Mark Waite Component/s: badge-plugin Component/s: other Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202336.1570115224000.673.1570115280764%40Atlassian.JIRA.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title pau sabats commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted I reproduced this error on win10 removing the slave-agent.jnlp or having more than 1 of this files. The problem is that the slaves loses somehow the connection configuration to the master so this error is shown. My solution was to create a new agent slave, so a new .jnlp can be downloaded, and this one will be well configured so it will work. If the .jnlp doesn't show you in jenkins to download, you can try with the command : java -jar agent.jar -jnlpUrl http://jenkinsurl:port/computer/windows-agent/slave-agent.jnlp -secret -workDir "C:\JenkinsSlave" Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164090.1437742638000.634.1570114681250%40Atlassian.JIRA.
[JIRA] (JENKINS-59484) EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Title: Message Title Karl Wirth edited a comment on JENKINS-59484 Re: EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory Have met with the developers: Concurrency bug =TBD. Sub-directory support is an enhancement request. To work around JENKINS-48882 we have to look at the directory name to figure out which executor we are on. If you use 'dir()' it breaks this check hence '0' every time. We will need a redesign of this check to allow for the it to work at lower levels and it will need to cope with Windows and Linux paths. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202099.1569244102000.632.1570114620147%40Atlassian.JIRA.
[JIRA] (JENKINS-59484) EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Title: Message Title Karl Wirth edited a comment on JENKINS-59484 Re: EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory Have met with the developers:Concurrency bug = JENKINS-58119 TBD. Sub-directory support is an enhancement request. To work around JENKINS-48882 we have to look at the directory name to figure out which executor we are on. If you use 'dir()' it breaks this check hence '0' every time. We will need a redesign of this check to allow for the it to work at lower levels and it will need to cope with Windows and Linux paths. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202099.1569244102000.628.1570114080331%40Atlassian.JIRA.
[JIRA] (JENKINS-59484) EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-59484 EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory Change By: Karl Wirth Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202099.1569244102000.630.1570114080388%40Atlassian.JIRA.
[JIRA] (JENKINS-59484) EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Title: Message Title Karl Wirth commented on JENKINS-59484 Re: EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory Have met with the developers: Concurrency bug = JENKINS-58119 Sub-directory support is an enhancement request. To work around JENKINS-48882 we have to look at the directory name to figure out which executor we are on. If you use 'dir()' it breaks this check hence '0' every time. We will need a redesign of this check to allow for the it to work at lower levels and it will need to cope with Windows and Linux paths. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202099.1569244102000.626.1570113960198%40Atlassian.JIRA.
[JIRA] (JENKINS-59645) Encoding problems after update to version 2.190.1
Title: Message Title Jonathan Gonçalves commented on JENKINS-59645 Re: Encoding problems after update to version 2.190.1 Added some error logs Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202335.1570113234000.624.1570113600264%40Atlassian.JIRA.
[JIRA] (JENKINS-58320) KeyGenerator without initialization
Title: Message Title Sergey Khokhlov assigned an issue to Sergey Khokhlov Jenkins / JENKINS-58320 KeyGenerator without initialization Change By: Sergey Khokhlov Assignee: Sergey Khokhlov Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200428.156215583.622.1570113600209%40Atlassian.JIRA.
[JIRA] (JENKINS-59645) Encoding problems after update to version 2.190.1
Title: Message Title Jonathan Gonçalves updated an issue Jenkins / JENKINS-59645 Encoding problems after update to version 2.190.1 Change By: Jonathan Gonçalves Attachment: jenkins.log Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202335.1570113234000.623.1570113600251%40Atlassian.JIRA.
[JIRA] (JENKINS-59645) Encoding problems after update to version 2.190.1
Title: Message Title Jonathan Gonçalves created an issue Jenkins / JENKINS-59645 Encoding problems after update to version 2.190.1 Issue Type: Bug Assignee: Unassigned Attachments: Capturar.PNG, Capturar2.PNG, image (3).png Components: _unsorted Created: 2019-10-03 14:33 Environment: Docker Image: jenkins / jenkins : 2.190.1 Using Blueocean and all default plugins in the latest version Priority: Major Reporter: Jonathan Gonçalves After update from 2.176.1 to 2.190.1 some projects with accents can't be access anymore because the Job link appears empty. Another problem is in Blueocean, that doesnt show project names with accents. Another problem is in the job execution, that throw an Exception when try to build projects with accents on name. Add Comment
[JIRA] (JENKINS-58949) If job fails in cleanup further triggering fails
Title: Message Title Karl Wirth commented on JENKINS-58949 Re: If job fails in cleanup further triggering fails Need to retest after changes in 10.0.1.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201296.1565876577000.620.1570113120131%40Atlassian.JIRA.
[JIRA] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title Jai Mishra commented on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) i have the same problem.Please let me know when are you planning to release this fix. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192737.1533040103000.605.1570112160948%40Atlassian.JIRA.
[JIRA] (JENKINS-59456) Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding
Title: Message Title KaiHsiang Chang updated JENKINS-59456 Jenkins / JENKINS-59456 Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding Change By: KaiHsiang Chang Status: Fixed but Unreleased Resolved Released As: https://github.com/jenkinsci/parameterized-remote-trigger-plugin/releases/tag/Parameterized-Remote-Trigger-3.1.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202049.1568954668000.599.1570112103493%40Atlassian.JIRA.
[JIRA] (JENKINS-59456) Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding
Title: Message Title KaiHsiang Chang closed an issue as Fixed fixed & released Jenkins / JENKINS-59456 Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding Change By: KaiHsiang Chang Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202049.1568954668000.602.1570112104082%40Atlassian.JIRA.
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Ryan Campbell commented on JENKINS-59644 Re: Upgrade Jenkins core pre-requisite to 2.138.4 1 Agree, we only support 2.138 now anyway. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202334.1570111402000.596.1570111920125%40Atlassian.JIRA.
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59644 Upgrade Jenkins core pre-requisite to 2.138.4 Change By: Arnaud Héritier + use BOM The idea will be to upgrade de support-core dependency too (it has the same requirement) With a more recent version of support-core we get more informations and we have less performances issues with the anonymisation (For now we require support-core 2.44 which doesn't propose the anonymisation) Any thoughts [~recampbell] ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202334.1570111402000.594.1570111742983%40Atlassian.JIRA.
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59644 Upgrade Jenkins core pre-requisite to 2.138.4 Change By: Arnaud Héritier + use BOM The idea will be to upgrade de support-core dependency too (it has the same requirement) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202334.1570111402000.589.1570111560495%40Atlassian.JIRA.
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59644 Upgrade Jenkins core pre-requisite to 2.138.4 Issue Type: Task Assignee: Arnaud Héritier Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-03 14:03 Priority: Minor Reporter: Arnaud Héritier + use BOM Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59629) Not validating the TOS is confusing
Title: Message Title Arnaud Héritier updated JENKINS-59629 Jenkins / JENKINS-59629 Not validating the TOS is confusing Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Released As: cloudbees-jenkins-advisor-plugin-2.11 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202310.1570035924000.587.1570111320243%40Atlassian.JIRA.
[JIRA] (JENKINS-59456) Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding
Title: Message Title KaiHsiang Chang updated JENKINS-59456 Fixed in b44fb12 Jenkins / JENKINS-59456 Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding Change By: KaiHsiang Chang Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To
[JIRA] (JENKINS-59456) Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding
Title: Message Title KaiHsiang Chang commented on JENKINS-59456 Re: Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding Fixed in b44fb12 , will be included in next release. BTW, Robert Platt, thanks for your mail & solution. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202049.1568954668000.578.1570110660288%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title tapvir virk edited a comment on JENKINS-59633 Re: EC2 Plguin: Windows EC2 instances are not launching Attaching the screenshot of the ec2 slave setting. Do you know which permission is required? Though I can see the instance getting launched on aws account. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202315.157004916.574.1570110360258%40Atlassian.JIRA.
[JIRA] (JENKINS-58639) pipeline job runs every two minutes
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-58639 pipeline job runs every two minutes Change By: Paul Allen Labels: P4_VERIFY P4_A Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200807.156396953.571.1570110300279%40Atlassian.JIRA.
[JIRA] (JENKINS-58639) pipeline job runs every two minutes
Title: Message Title Paul Allen started work on JENKINS-58639 Change By: Paul Allen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200807.156396953.567.1570110240557%40Atlassian.JIRA.
[JIRA] (JENKINS-58639) pipeline job runs every two minutes
Title: Message Title Paul Allen assigned an issue to Charusheela Bopardikar Jenkins / JENKINS-58639 pipeline job runs every two minutes Change By: Paul Allen Assignee: Charusheela Bopardikar Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200807.156396953.564.1570110240469%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title tapvir virk commented on JENKINS-59633 Re: EC2 Plguin: Windows EC2 instances are not launching Attaching the screenshot of the ec2 slave setting. Do you know which permission is required? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202315.157004916.558.1570110120174%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title tapvir virk updated an issue Jenkins / JENKINS-59633 EC2 Plguin: Windows EC2 instances are not launching Change By: tapvir virk Attachment: access_denied_windows_ec2_plugin.gif Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202315.157004916.554.1570110060233%40Atlassian.JIRA.
[JIRA] (JENKINS-33708) Invocation of 'sh' on Windows should provide a more helpful error
Title: Message Title pau sabats commented on JENKINS-33708 Re: Invocation of 'sh' on Windows should provide a more helpful error The error related with : Cannot run program "nohup" means that it's searching for nohup.exe because is what jenkins requires when using 'sh' in the pipeline, so you can use nuhup.exe from here: "C:\Program Files\Git\usr\bin". Eventhough, what I have done in order to solve this issue is the following: Create a if else statement in your jenkinsfile that does: if (isUnix()) --> sh "command" else --> bat "command" doing so the pipeline running on agent windows will run as bat and this error no longer appears. Note: You can also use "tool config configuration" of jenkins and install tools from there. In case your sh commands were related with installation files Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169163.1458600265000.528.1570107300956%40Atlassian.JIRA.
[JIRA] (JENKINS-59613) Rename the plugin "Jenkins Health Advisor by CloudBees"
Title: Message Title Arnaud Héritier updated JENKINS-59613 Jenkins / JENKINS-59613 Rename the plugin "Jenkins Health Advisor by CloudBees" Change By: Arnaud Héritier Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202254.1569951438000.525.1570106820546%40Atlassian.JIRA.
[JIRA] (JENKINS-57138) Performance issue due to the bundle anonymization
Title: Message Title Arnaud Héritier commented on JENKINS-57138 Re: Performance issue due to the bundle anonymization FYI Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1555935767000.522.1570106820416%40Atlassian.JIRA.
[JIRA] (JENKINS-33628) Support bundle corrupt via UI
Title: Message Title Arnaud Héritier resolved as Fixed Jenkins / JENKINS-33628 Support bundle corrupt via UI Change By: Arnaud Héritier Status: In Progress Resolved Resolution: Fixed Released As: support-core-2.57 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169075.145823170.517.1570106580868%40Atlassian.JIRA.
[JIRA] (JENKINS-59048) Config as Code plugin throws exception when trying to read spotBlockReservationDurationStr from EC2 agent when spot instance enabled.
Title: Message Title Gunter Grodotzki updated an issue Jenkins / JENKINS-59048 Config as Code plugin throws exception when trying to read spotBlockReservationDurationStr from EC2 agent when spot instance enabled. Change By: Gunter Grodotzki Component/s: configuration-as-code-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201402.156646108.512.1570102020268%40Atlassian.JIRA.
[JIRA] (JENKINS-59643) parameter store plugin doesn't use instance profile or assumed role
Title: Message Title robin yonge created an issue Jenkins / JENKINS-59643 parameter store plugin doesn't use instance profile or assumed role Issue Type: Bug Assignee: Rik Turnbull Components: aws-parameter-store-plugin Created: 2019-10-03 10:30 Priority: Minor Reporter: robin yonge Hi! I understand this probably isn't a bug but I couldn't find anywhere else to ask a question. I want to be able to fetch parameters using either a role assumed with the `withAWS` build step provided in the pipeline-aws plugin, or to use the instance profile on the Jenkins node, but this doesn't seem to work?? Is there something I'm missing? Add Comment
[JIRA] (JENKINS-59456) Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding
Title: Message Title
Robert Platt commented on JENKINS-59456
Re: Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding
After a Tomcat upgrade, this affected us too. As a workaround, we added {{relaxedQueryChars="[,]" }}in the remote Tomcat's server.xml
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202049.1568954668000.507.1570097761221%40Atlassian.JIRA.
[JIRA] (JENKINS-59642) implement organizationChildTriggersProperty
Title: Message Title Ewelina Wilkosz assigned an issue to Daniel Spilker Jenkins / JENKINS-59642 implement organizationChildTriggersProperty Change By: Ewelina Wilkosz Assignee: Ewelina Wilkosz Daniel Spilker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202324.1570095021000.504.1570096620403%40Atlassian.JIRA.
[JIRA] (JENKINS-59642) implement organizationChildTriggersProperty
Title: Message Title
Gunter Grodotzki updated an issue
Jenkins / JENKINS-59642
implement organizationChildTriggersProperty
Change By:
Gunter Grodotzki
would be great to configure organizationChildTriggersProperty via CasC , like so maybe? {code:java}organizationChildTriggersProperty { templates { interval('1h') }}{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202324.1570095021000.501.1570096080212%40Atlassian.JIRA.
[JIRA] (JENKINS-59642) implement organizationChildTriggersProperty
Title: Message Title Gunter Grodotzki updated an issue Jenkins / JENKINS-59642 implement organizationChildTriggersProperty Change By: Gunter Grodotzki Component/s: branch-api-plugin Component/s: job-dsl-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202324.1570095021000.497.1570096021181%40Atlassian.JIRA.
[JIRA] (JENKINS-59642) implement organizationChildTriggersProperty
Title: Message Title Gunter Grodotzki updated an issue Jenkins / JENKINS-59642 implement organizationChildTriggersProperty Change By: Gunter Grodotzki Component/s: configuration-as-code-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202324.1570095021000.499.1570096021337%40Atlassian.JIRA.
[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title trinadh teegala commented on JENKINS-59542 Re: There is problem while I'm trying to give CIFS share builds in Jenkins Hi Alex, Please let me know Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202172.1569500879000.495.1570095720203%40Atlassian.JIRA.
[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title trinadh teegala assigned an issue to Alex Earl Jenkins / JENKINS-59542 There is problem while I'm trying to give CIFS share builds in Jenkins Change By: trinadh teegala Assignee: Alex Earl Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202172.1569500879000.493.1570095720177%40Atlassian.JIRA.
[JIRA] (JENKINS-39874) Abilty to disable pipeline-replay in Job Configuration.
Title: Message Title Larkoie commented on JENKINS-39874 Re: Abilty to disable pipeline-replay in Job Configuration. Jesse Glick I'm having the same issue. I'd like to prevent "replay" option on my pipelines but any user with "Job - Build" right also have the replay right. (bellow is a screenshot of their rights. In the global config the only permission they have is the global Read permission which is mandatory to access Jenkins UI) : Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176488.1479513265000.484.1570095600287%40Atlassian.JIRA.
[JIRA] (JENKINS-39874) Abilty to disable pipeline-replay in Job Configuration.
Title: Message Title Larkoie updated an issue Jenkins / JENKINS-39874 Abilty to disable pipeline-replay in Job Configuration. Change By: Larkoie Attachment: image-2019-10-03-11-38-21-093.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176488.1479513265000.475.1570095540466%40Atlassian.JIRA.
