[JIRA] (JENKINS-53957) hpi bundles transitive dependencies of test scope dependencies
Title: Message Title Pavel Roskin commented on JENKINS-53957 Re: hpi bundles transitive dependencies of test scope dependencies Bitbucket Server Notifier Plugin version 1.9 is also affected. It packages sshd-core-0.14.0.jar unnecessarily. "mvn dependency:tree" shows: [INFO] +- org.jenkins-ci.main:jenkins-war:executable-war:2.60.3:test [INFO] | +- org.jenkins-ci.modules:instance-identity:jar:2.1:test [INFO] | | \- io.github.stephenc.crypto:self-signed-cert-generator:jar:1.0.0:test [INFO] | +- org.jenkins-ci.modules:ssh-cli-auth:jar:1.4:test [INFO] | +- org.jenkins-ci.modules:slave-installer:jar:1.5:test [INFO] | +- org.jenkins-ci.modules:windows-slave-installer:jar:1.9:test [INFO] | +- org.jenkins-ci.modules:launchd-slave-installer:jar:1.2:test [INFO] | +- org.jenkins-ci.modules:upstart-slave-installer:jar:1.1:test [INFO] | +- org.jenkins-ci.modules:systemd-slave-installer:jar:1.1:test [INFO] | +- org.jenkins-ci.modules:sshd:jar:1.11:test [INFO] | | \- org.apache.sshd:sshd-core:jar:0.14.0:compile That goes against the rule that the dependencies of test dependencies are either test dependencies or not dependencies at all. A way to remove that dependency from the hpi is to declare it explicitly as a test dependency. However, that would be a hack, not a solution. maven-hpi-plugin should either follow the dependency rule or warn loudly (and fail optionally) if it cannot follow that rule for whatever reason, so that the issue could be mitigated right away. Please reopen the ticket, I don't see any reason to close it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-48881) Stage still shown with NaNy NaNd when condition returns false
Title: Message Title Basil Crow commented on JENKINS-48881 Re: Stage still shown with NaNy NaNd when condition returns false Likely fixed by jenkinsci/pipeline-stage-view-plugin#68. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187676.151558985.4422.1564531980417%40Atlassian.JIRA.
[JIRA] (JENKINS-58592) Detecting annotation processors on the compile classpath has been deprecated (Gradle 5.0)
Title: Message Title Steve Hill resolved as Fixed Jenkins / JENKINS-58592 Detecting annotation processors on the compile classpath has been deprecated (Gradle 5.0) Change By: Steve Hill Status: Open Resolved Resolution: Fixed Released As: 0.28.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200749.1563778095000.4419.1564527900243%40Atlassian.JIRA.
[JIRA] (JENKINS-58592) Detecting annotation processors on the compile classpath has been deprecated (Gradle 5.0)
Title: Message Title Steve Hill commented on JENKINS-58592 Re: Detecting annotation processors on the compile classpath has been deprecated (Gradle 5.0) Hi Arno Moonen, this was fixed with version 0.28.0 of the gradle-jpi-plugin on 2018-11-26. The plugin is currently built and consumed on Gradle 5.5. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200749.1563778095000.4417.1564527840098%40Atlassian.JIRA.
[JIRA] (JENKINS-52806) Pipeline: Parallel syncs don't set environment variables properly.
Title: Message Title William Brode commented on JENKINS-52806 Re: Pipeline: Parallel syncs don't set environment variables properly. To celebrate the one year anniversary of this bug - I've opened a pull request https://github.com/jenkinsci/p4-plugin/pull/104 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192727.153298856.4415.1564526460330%40Atlassian.JIRA.
[JIRA] (JENKINS-52806) Pipeline: Parallel syncs don't set environment variables properly.
Title: Message Title William Brode assigned an issue to William Brode Jenkins / JENKINS-52806 Pipeline: Parallel syncs don't set environment variables properly. Change By: William Brode Assignee: Matthew Smeeth William Brode Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192727.153298856.4402.1564525560288%40Atlassian.JIRA.
[JIRA] (JENKINS-53067) Android App Bundle upload support
Title: Message Title Joe Hansche commented on JENKINS-53067 Re: Android App Bundle upload support The update to the v3 SDK has been merged and released under plugin v2.0. I've started working on including AAB support – starting with some basic unit tests for now, before starting a larger refactor. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193060.1534426687000.4383.1564524120741%40Atlassian.JIRA.
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title Karl Shultz commented on JENKINS-58717 Re: Modify ATH to be compatible with new GitHub Branch Source UI I've got a simple pull request up for review that adds the ability to set a single repository URL from a test, via the new field in GitHub Branch Source 2.5.5. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201009.1564432009000.4380.1564520580215%40Atlassian.JIRA.
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title Karl Shultz updated JENKINS-58717 Jenkins / JENKINS-58717 Modify ATH to be compatible with new GitHub Branch Source UI Change By: Karl Shultz Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201009.1564432009000.4381.1564520580260%40Atlassian.JIRA.
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title Karl Shultz commented on JENKINS-58717 Re: Modify ATH to be compatible with new GitHub Branch Source UI I found a way to get past this, so I'm no longer blocked against 58071. But 58071 is still worth looking at. The behavior was, when working on the ATH from IntelliJ IDEA, I wanted to set an environment variable specifying a war file. Something like this: JENKINS_LOCAL_HOSTNAME=127.0.0.1;BROWSER=chrome;JENKINS_WAR=/some/path/to/jenkins.war When running that way, I was having problems getting the UI to load correctly. The trace itself can be seen here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201009.1564432009000.4379.1564520520112%40Atlassian.JIRA.
[JIRA] (JENKINS-58734) DefaultCrumbIssuer should use more secure hashing algorithm
Title: Message Title Matt Sicker updated JENKINS-58734 Jenkins / JENKINS-58734 DefaultCrumbIssuer should use more secure hashing algorithm Change By: Matt Sicker Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201034.1564513818000.4377.1564519320106%40Atlassian.JIRA.
[JIRA] (JENKINS-58734) DefaultCrumbIssuer should use more secure hashing algorithm
Title: Message Title Matt Sicker commented on JENKINS-58734 Re: DefaultCrumbIssuer should use more secure hashing algorithm See https://github.com/jenkinsci/jenkins/pull/4134 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201034.1564513818000.4378.1564519320154%40Atlassian.JIRA.
[JIRA] (JENKINS-58722) Invalid ssh remote url
Title: Message Title Parichay Barpanda updated JENKINS-58722 Jenkins / JENKINS-58722 Invalid ssh remote url Change By: Parichay Barpanda Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201014.1564470656000.4364.1564516561215%40Atlassian.JIRA.
[JIRA] (JENKINS-58680) Origin MR Trait and Fork Trait working is swapped
Title: Message Title Parichay Barpanda updated JENKINS-58680 Jenkins / JENKINS-58680 Origin MR Trait and Fork Trait working is swapped Change By: Parichay Barpanda Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200962.1564146247000.4362.1564516561168%40Atlassian.JIRA.
[JIRA] (JENKINS-58593) SCMHeadEvent is not fired in webhook
Title: Message Title Parichay Barpanda started work on JENKINS-58593 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200750.1563780141000.4365.1564516561226%40Atlassian.JIRA.
[JIRA] (JENKINS-58666) Add Trusted contributor trait to ForkMRTraits
Title: Message Title Parichay Barpanda updated JENKINS-58666 Jenkins / JENKINS-58666 Add Trusted contributor trait to ForkMRTraits Change By: Parichay Barpanda Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200948.156408612.4361.1564516561106%40Atlassian.JIRA.
[JIRA] (JENKINS-58695) Allow group projects fetch for user owner
Title: Message Title Parichay Barpanda updated JENKINS-58695 Jenkins / JENKINS-58695 Allow group projects fetch for user owner Change By: Parichay Barpanda Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200984.1564328712000.4363.1564516561194%40Atlassian.JIRA.
[JIRA] (JENKINS-58730) Add httpRemote variable to GitLabSCMSource
Title: Message Title Parichay Barpanda updated JENKINS-58730 Jenkins / JENKINS-58730 Add httpRemote variable to GitLabSCMSource Change By: Parichay Barpanda Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201025.156448998.4359.1564516500188%40Atlassian.JIRA.
[JIRA] (JENKINS-58377) Add instructions for multibranch pipeline jobs
Title: Message Title Parichay Barpanda updated JENKINS-58377 Jenkins / JENKINS-58377 Add instructions for multibranch pipeline jobs Change By: Parichay Barpanda Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200498.1562590092000.4360.1564516500251%40Atlassian.JIRA.
[JIRA] (JENKINS-58734) DefaultCrumbIssuer should use more secure hashing algorithm
Title: Message Title Matt Sicker created an issue Jenkins / JENKINS-58734 DefaultCrumbIssuer should use more secure hashing algorithm Issue Type: Improvement Assignee: Matt Sicker Components: core Created: 2019-07-30 19:10 Priority: Minor Reporter: Matt Sicker The default crumb issuer for Jenkins uses an MD5 hash of some state data to create a crumb for users. This may be hypothetically vulnerable to brute forcing of MD5 hashes to form a valid crumb if the crumb's state is predictable to some level of detail (unsure on the specifics, hence why it's just hypothetical). This is most predictable when the administrator excludes remote IP address and session ID information from being used to seed the crumb, so it's a somewhat contrived scenario potentially. This can be hardened by simply updating the message digest algorithm chosen. Since all JDKs must support SHA-256 as well, this seems like a reasonable update. Add Comment
[JIRA] (JENKINS-58734) DefaultCrumbIssuer should use more secure hashing algorithm
Title: Message Title Matt Sicker started work on JENKINS-58734 Change By: Matt Sicker Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201034.1564513818000.4351.1564513860174%40Atlassian.JIRA.
[JIRA] (JENKINS-41845) Suppress default pipeline output
Title: Message Title Ravi Godavarthi edited a comment on JENKINS-41845 Re: Suppress default pipeline output I use scripted pipelines heavily and I think the ability to toggle these lines as an option is really useful, removing a lot of clutter from logs and improving productivity.Its nearly impossible to click hide of hundreds of blocks I have in large pipelines and also Blueocean's declarative pipelines is not an option as its not meant for advanced/ complex pipelines and is only for pipeline rookies (simpler, application oriented use-cases)[~jglick] I am an experienced used user of scripted pipelines but new to plugin development, let me know how I can help and I'll be happy to spend time on this Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178692.1486564607000.4333.1564512180975%40Atlassian.JIRA.
[JIRA] (JENKINS-41845) Suppress default pipeline output
Title: Message Title Ravi Godavarthi commented on JENKINS-41845 Re: Suppress default pipeline output I use scripted pipelines heavily and I think the ability to toggle these lines as an option is really useful, removing a lot of clutter from logs and improving productivity. Its nearly impossible to click hide of hundreds of blocks I have in large pipelines and also Blueocean's declarative pipelines is not an option as its not meant for advanced/ complex pipelines and is only for pipeline rookies (simpler, application oriented use-cases) Jesse Glick I am an experienced used of scripted pipelines but new to plugin development, let me know how I can help and I'll be happy to spend time on this Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178692.1486564607000.4331.1564512180951%40Atlassian.JIRA.
[JIRA] (JENKINS-58729) Extended security settings plugin cannot be configured
Title: Message Title Matt Sicker updated JENKINS-58729 Fixed and released in extended-security-settings 1.1. Jenkins / JENKINS-58729 Extended security settings plugin cannot be configured Change By: Matt Sicker Status: Fixed but Unreleased Resolved Released As: extended-security-settings-1.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201024.1564489867000.4314.1564512000128%40Atlassian.JIRA.
[JIRA] (JENKINS-58729) Extended security settings plugin cannot be configured
Title: Message Title Matt Sicker updated JENKINS-58729 Jenkins / JENKINS-58729 Extended security settings plugin cannot be configured Change By: Matt Sicker Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201024.1564489867000.4312.1564511700245%40Atlassian.JIRA.
[JIRA] (JENKINS-57265) SCM Skip doesn't abort my docker builds until much later
Title: Message Title ipleten edited a comment on JENKINS-57265 Re: SCM Skip doesn't abort my docker builds until much later I can't find any non- "hacky" approach how to exclude commit from build on message content . None of plugins seems work with multibranch pipelines. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199030.1556653885000.4310.1564511160154%40Atlassian.JIRA.
[JIRA] (JENKINS-57265) SCM Skip doesn't abort my docker builds until much later
Title: Message Title ipleten commented on JENKINS-57265 Re: SCM Skip doesn't abort my docker builds until much later I can't find any "hacky" approach how to exclude commit from build. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199030.1556653885000.4307.1564511100240%40Atlassian.JIRA.
[JIRA] (JENKINS-57265) SCM Skip doesn't abort my docker builds until much later
Title: Message Title ipleten updated an issue Jenkins / JENKINS-57265 SCM Skip doesn't abort my docker builds until much later Change By: ipleten Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199030.1556653885000.4304.1564511040286%40Atlassian.JIRA.
[JIRA] (JENKINS-57265) SCM Skip doesn't abort my docker builds until much later
Title: Message Title ipleten commented on JENKINS-57265 Re: SCM Skip doesn't abort my docker builds until much later I have the same issue with kubernetes plugin. ScmSkip matches the pattern but still continues with pipeline! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199030.1556653885000.4301.1564510800346%40Atlassian.JIRA.
[JIRA] (JENKINS-35509) ci skip is not working
Title: Message Title ipleten commented on JENKINS-35509 Re: ci skip is not working Is there any plans about working on that plugin? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171317.146549440.4295.1564509960237%40Atlassian.JIRA.
[JIRA] (JENKINS-56581) org.jenkinsci.remoting.protocol.IOHub takes 100% CPU
Title: Message Title Jeff Thompson commented on JENKINS-56581 Re: org.jenkinsci.remoting.protocol.IOHub takes 100% CPU Jörg Sautter, so updating to Java 11 resolved this for you? That's great information. Any reason not to close this information, then? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198196.1552647394000.4290.1564509660231%40Atlassian.JIRA.
[JIRA] (JENKINS-56029) Kubernetes Plugin: Concurrent builds do not have their own unique workspaces
Title: Message Title
James Nelson commented on JENKINS-56029
Re: Kubernetes Plugin: Concurrent builds do not have their own unique workspaces
Curious if there's any more details on this? We're seeing a similar issue. Are you using `node(POD_LABEL)` or just going straight to `container('containerName')`?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197449.1549559392000.4287.1564506420258%40Atlassian.JIRA.
[JIRA] (JENKINS-58289) Release version 2.0
Title: Message Title Long Nguyen resolved as Done Jenkins / JENKINS-58289 Release version 2.0 Change By: Long Nguyen Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200353.1562008792000.4285.1564505520464%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Jesse Glick commented on JENKINS-49278 Re: cat command in docker agents not detected correctly agent docker is just sugar for withDockerContainer. The expected use case is anything that happens to work the first time you try it. There is really no further guarantee than that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.4245.1564504140794%40Atlassian.JIRA.
[JIRA] (JENKINS-58733) Cannot delete project
Title: Message Title Ferdinand Stapenhorst created an issue Jenkins / JENKINS-58733 Cannot delete project Issue Type: Task Assignee: Unassigned Components: core Created: 2019-07-30 16:23 Environment: Jenkins v 2.187 on Windows Server 2012 R2 running Java Version 8 update 211 Labels: deletion Priority: Minor Reporter: Ferdinand Stapenhorst I am trying to simply delete a project and I get the following exception. I tried on 4 different projects and It happens on every project. When looking on the file system, a file called permalinks is in the folder and a handle is open from java.exe that belongs to jenkins. Before I attempt to delete the project, the handle did not exist. I also tried to manually close the handle (using Sysinternals Process Explorer) and tried again - with no success. The handle appears again. jenkins.util.io.CompositeIOException: Unable to delete 'c:\jenkins\jobs\Drivve Print Setup 3.4'. Tried 3 times (of a maximum of 3) waiting 0.1 Sekunden between attempts. at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:99) at hudson.Util.deleteRecursive(Util.java:293) at hudson.Util.deleteRecursive(Util.java:282) at hudson.model.AbstractItem.performDelete(AbstractItem.java:791) at hudson.model.AbstractProject.performDelete(AbstractProject.java:362) at hudson.model.AbstractItem.delete(AbstractItem.java:775) at hudson.model.Job.delete(Job.java:676) at hudson.model.AbstractItem.doDoDelete(AbstractItem.java:645) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Ad edited a comment on JENKINS-49278
Re: cat command in docker agents not detected correctly
Well, we are using the Docker agent syntax:{code:java}agent { docker { image 'ag/ubuntu-conan' args '''-v $DOCKERCONFIG_FOLDER/ag/ubuntu-conan.env:/dockerconfig.env } }stage('Use the tool') { steps {sh 'conan install whatever' }}{code}Is not that the exact intended "tool-only" use case you were mentioning above? If not, what is the expected use-case for these kind of agents then?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.4210.1564502582311%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Ad commented on JENKINS-49278
Re: cat command in docker agents not detected correctly
Well, we are using the Docker agent syntax:
agent {
docker {
image 'ag/ubuntu-conan'
args '''-v $DOCKERCONFIG_FOLDER/ag/ubuntu-conan.env:/dockerconfig.env
}
}
stage('Use the tool') {
steps {
sh 'conan install whatever'
}
}
Is not that the exact intended "tool-only" use case you were mentioning above? If not, what is the expected use-case for these kind of agents then?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.4208.1564502582248%40Atlassian.JIRA.
[JIRA] (JENKINS-39862) Make stash/unstash work in container.inside
Title: Message Title Javier G. Sogo commented on JENKINS-39862 Re: Make stash/unstash work in container.inside Julien Pivotto, I would like to know how you managed to do it, I think this is what I need (stash from docker.inside) but maybe there is a better alternative. Thanks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176460.1479463738000.4174.1564502460098%40Atlassian.JIRA.
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title Karl Shultz started work on JENKINS-58717 Change By: Karl Shultz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201009.1564432009000.4172.1564502340089%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Jesse Glick commented on JENKINS-49278 Re: cat command in docker agents not detected correctly For specialized use cases like this you should not use withDockerContainer. Just run whatever docker commands you need directly from a sh (or indirectly via some script). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.4139.1564502040716%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Ad commented on JENKINS-49278 Re: cat command in docker agents not detected correctly Jesse Glick It is very undestandable that `withDockerContainer` is expected for tool-only images, and as a matter of fact that is exactly what our organization uses it for. Yet, such tool-only container can very easily have an ` ENTRYPOINT` which needs to completely run before the actual sh steps are executed. In our case, we have a Docker container that we use as a Conan (https://conan.io/) tool. Yet, this container has a entrypoint which runs the usual `docker-entrypoint.sh` that is notably responsible for setting up the different remote repositories and log-in to use them. Yet, we observe spurious failure because of the race condition: sometimes the entrypoint had time to complete before the sh steps are executed, sometimes it did not. The problem is clearly addressed by the Docker guidelines: `ENTRYPOINT` is for the container steps that should not be replaced by the client, and `CMD` is exactly for client override. It does not seem reasonable for Docker to execute commands while racing with `ENTRYPOINT`, and it is becoming such a major problem for us that we will have to walk away from this solution if the situation remains as it currently is. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.4105.1564501801974%40Atlassian.JIRA.
[JIRA] (JENKINS-58729) Extended security settings plugin cannot be configured
Title: Message Title Matt Sicker updated JENKINS-58729 Jenkins / JENKINS-58729 Extended security settings plugin cannot be configured Change By: Matt Sicker Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201024.1564489867000.4103.1564501440258%40Atlassian.JIRA.
[JIRA] (JENKINS-58729) Extended security settings plugin cannot be configured
Title: Message Title Matt Sicker started work on JENKINS-58729 Change By: Matt Sicker Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201024.1564489867000.4101.1564501440224%40Atlassian.JIRA.
[JIRA] (JENKINS-58732) Invert pipeline-model-definition → docker-workflow dependency
Title: Message Title Jesse Glick commented on JENKINS-58732 Re: Invert pipeline-model-definition → docker-workflow dependency Pending JENKINS-49651, delivering this to existing installations might be tricky as users might update some but not all plugins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201031.1564500516000.4097.1564500960145%40Atlassian.JIRA.
[JIRA] (JENKINS-58732) Invert pipeline-model-definition → docker-workflow dependency
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-58732 Invert pipeline-model-definition → docker-workflow dependency Issue Type: Task Assignee: Andrew Bayer Components: docker-workflow-plugin, pipeline-model-definition-plugin Created: 2019-07-30 15:28 Priority: Minor Reporter: Jesse Glick Currently pipeline-model-definition has a dependency on docker-workflow to supply agent docker and agent dockerfile definitions. These should rather be defined in the docker-workflow plugin, which would then get a dependency on pipeline-model-extensions (unclear if that should be optional). This would match, for example, how agent kubernetes is defined in the kubernetes plugin, and how I propose (related to JENKINS-48050) something like agent dockerNode should be defined in the docker plugin, keeping the sensitive aspects of the behavior close to the plugin which manages that environment. It would also allow docker-workflow to be omitted from distributions which do not need it. In particular, Kubernetes-oriented distributions are unlikely to have any use for agent docker. (You might want to install docker-workflow so as to be able to use withDockerContainer with DinD, but in that case you would still be using agent kubernetes, and anyway the most common use case—building Docker images—is preferably handled via Kaniko.)
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title Karl Shultz commented on JENKINS-58717 Re: Modify ATH to be compatible with new GitHub Branch Source UI Assigning to myself. I'm currently blocked by JENKINS-58071. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201009.1564432009000.4091.1564499100044%40Atlassian.JIRA.
[JIRA] (JENKINS-57495) Publish with ssh plugin does not work with openssh key
Title: Message Title Taehyung Lim commented on JENKINS-57495 Re: Publish with ssh plugin does not work with openssh key I had the same issue and solved. The problem is private key file format. This is my private key header. This is from ssh-keygen on Macbook, not from puttygen. -BEGIN OPENSSH PRIVATE KEY- b3Blb "BEGIN OPENSSH" and "b3Blb" means the "newer OpenSSH format". Jenkins or plugin failed to read this format. If you want to make "older" OpenSSH format, try this. Or make your keys by using old ssh-keygen. ssh-keygen -t rsa -b 4096 -m PEM Your new private key should looks like this. -BEGIN RSA PRIVATE KEY- MIIE ps. You can't use ed25519 algorithm. Because ed25519 needs newer format. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-58730) Add httpRemote variable to GitLabSCMSource
Title: Message Title Parichay Barpanda started work on JENKINS-58730 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201025.156448998.4082.1564498740249%40Atlassian.JIRA.
[JIRA] (JENKINS-58730) Add httpRemote variable to GitLabSCMSource
Title: Message Title Parichay Barpanda updated JENKINS-58730 Jenkins / JENKINS-58730 Add httpRemote variable to GitLabSCMSource Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201025.156448998.4083.1564498740294%40Atlassian.JIRA.
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title Karl Shultz assigned an issue to Karl Shultz Jenkins / JENKINS-58717 Modify ATH to be compatible with new GitHub Branch Source UI Change By: Karl Shultz Assignee: Oliver Gondža Karl Shultz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201009.1564432009000.4085.1564498740349%40Atlassian.JIRA.
[JIRA] (JENKINS-58666) Add Trusted contributor trait to ForkMRTraits
Title: Message Title Parichay Barpanda updated JENKINS-58666 Jenkins / JENKINS-58666 Add Trusted contributor trait to ForkMRTraits Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200948.156408612.4060.1564497900079%40Atlassian.JIRA.
[JIRA] (JENKINS-58730) Add httpRemote variable to GitLabSCMSource
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-58730 Add httpRemote variable to GitLabSCMSource Change By: Parichay Barpanda Summary: [FUTURE] Add httpRemote variable to GitLabSCMSource Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201025.156448998.4059.1564497780060%40Atlassian.JIRA.
[JIRA] (JENKINS-58730) [FUTURE] Add httpRemote variable to GitLabSCMSource
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-58730 [FUTURE] Add httpRemote variable to GitLabSCMSource Change By: Parichay Barpanda Summary: [FUTURE] Add http url httpRemote variable to GitLabSCMSource Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201025.156448998.4058.1564497720058%40Atlassian.JIRA.
[JIRA] (JENKINS-45047) Easy way to run integration tests in plugin repositories
Title: Message Title Jesse Glick commented on JENKINS-45047 Re: Easy way to run integration tests in plugin repositories if we implement JENKINS-47498 some of this might be easier to handle Currently the BOM uses POM properties to define versions only for plugins with tests JARs, but we can see that when this is done, the dependency tree of a plugin importing the BOM can be adjusted without touching pom.xml (just like we could already do with jenkins.version): kubernetes-plugin$ mvn dependency:tree | fgrep scm-api; mvn -Dscm-api-plugin.version=2.6.2 dependency:tree | fgrep scm-api [INFO] | \- org.jenkins-ci.plugins:scm-api:jar:2.6.3:compile [INFO] +- org.jenkins-ci.plugins:scm-api:jar:tests:2.6.3:test [INFO] | \- org.jenkins-ci.plugins:scm-api:jar:2.6.2:compile [INFO] +- org.jenkins-ci.plugins:scm-api:jar:tests:2.6.2:test Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183137.1498080984000.4053.1564496880460%40Atlassian.JIRA.
[JIRA] (JENKINS-45047) Easy way to run integration tests in plugin repositories
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-45047 Easy way to run integration tests in plugin repositories Change By: Jesse Glick Component/s: bom Component/s: maven-hpi-plugin Component/s: plugin-compat-tester Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183137.1498080984000.4054.1564496880472%40Atlassian.JIRA.
[JIRA] (JENKINS-51327) Random java.lang.NumberFormatException
Title: Message Title Erwan MATHIEU commented on JENKINS-51327 Re: Random java.lang.NumberFormatException Hi, just for the update, still present in version 2.176.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190665.1526379873000.4049.1564496520240%40Atlassian.JIRA.
[JIRA] (JENKINS-58690) Add retention strategy for Cloud
Title: Message Title Andrey Falko commented on JENKINS-58690 Re: Add retention strategy for Cloud This is retention of how long a node stays alive in the system. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200979.1564304727000.4046.1564496280095%40Atlassian.JIRA.
[JIRA] (JENKINS-57898) Write unit tests for implemented functions
Title: Message Title Andrey Falko started work on JENKINS-57898 Change By: Andrey Falko Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199862.1559851326000.4044.1564496220180%40Atlassian.JIRA.
[JIRA] (JENKINS-57668) Implement Cloud API to provision Kafka agents
Title: Message Title Andrey Falko updated JENKINS-57668 Jenkins / JENKINS-57668 Implement Cloud API to provision Kafka agents Change By: Andrey Falko Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199601.1558718371000.4042.1564496040441%40Atlassian.JIRA.
[JIRA] (JENKINS-45818) Metadata for Pipeline Stages and Steps
Title: Message Title Raúl Herrera Gil updated an issue Jenkins / JENKINS-45818 Metadata for Pipeline Stages and Steps Change By: Raúl Herrera Gil Epic Color: ghx-label- 6 3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184028.1501109332000.4036.1564495920341%40Atlassian.JIRA.
[JIRA] (JENKINS-58513) Flake in RestartPipelineTest#terminatedPodAfterRestart
Title: Message Title Jesse Glick commented on JENKINS-58513 Re: Flake in RestartPipelineTest#terminatedPodAfterRestart permalink Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200657.156327728.4034.1564493641150%40Atlassian.JIRA.
[JIRA] (JENKINS-58513) Flake in RestartPipelineTest#terminatedPodAfterRestart
Title: Message Title Vincent Latombe edited a comment on JENKINS-58513 Re: Flake in RestartPipelineTest#terminatedPodAfterRestart [~jglick] while attempting to track down the root cause, I saw that in the failure cases it was running [this| https://github.com/jenkinsci/workflow-durable-task-step-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java #L265] line. Since it runs asynchronously, this is probably a race condition with the thread handling node deletion. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200657.156327728.4032.1564493520910%40Atlassian.JIRA.
[JIRA] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Title: Message Title Andrew Dean updated an issue Jenkins / JENKINS-18162 Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects Change By: Andrew Dean Comment: I'm getting this issue with up to date plugins and it is 2019... I have an upstream job calling a downstream one and it occasionally figures out what to do with parameters but other times it pretends like they don't exist and executes anyway. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.149460.1370020502000.4022.1564492500390%40Atlassian.JIRA.
[JIRA] (JENKINS-58513) Flake in RestartPipelineTest#terminatedPodAfterRestart
Title: Message Title Vincent Latombe edited a comment on JENKINS-58513 Re: Flake in RestartPipelineTest#terminatedPodAfterRestart [~jglick] while attempting to track down the root cause, I saw that in the failure cases it was running [this|#L265] ] line. Since it runs asynchronously, this is probably a race condition with the thread handling node deletion. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200657.156327728.4019.1564491420808%40Atlassian.JIRA.
[JIRA] (JENKINS-58513) Flake in RestartPipelineTest#terminatedPodAfterRestart
Title: Message Title Vincent Latombe edited a comment on JENKINS-58513 Re: Flake in RestartPipelineTest#terminatedPodAfterRestart [~jglick] while attempting to track down the root cause, I saw that in the failure cases it was running [this| [https://github.com/jenkinsci/workflow-durable-task-step-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java #L265]] line. Since it runs asynchronously, this is probably a race condition with the thread handling node deletion. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200657.156327728.4016.1564491420460%40Atlassian.JIRA.
[JIRA] (JENKINS-58513) Flake in RestartPipelineTest#terminatedPodAfterRestart
Title: Message Title Vincent Latombe commented on JENKINS-58513 Re: Flake in RestartPipelineTest#terminatedPodAfterRestart Jesse Glick while attempting to track down the root cause, I saw that in the failure cases it was running this line. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200657.156327728.4013.1564491360174%40Atlassian.JIRA.
[JIRA] (JENKINS-58731) Separate site name from hostname
Title: Message Title Magnus Reftel created an issue Jenkins / JENKINS-58731 Separate site name from hostname Issue Type: Improvement Assignee: Joe Hansche Components: confluence-publisher-plugin Created: 2019-07-30 12:44 Priority: Minor Reporter: Magnus Reftel As it is today, the name of a site is the same as its hostname. That means that if the site changes hostname, then every pipeline must be updated to use the new site name. It would be much nicer if sites could be named (like servers in the Jira and Bitbucket plugins etc. are), so that the pipelines don't need to be modified for what is essentially a configuration change. Add Comment
[JIRA] (JENKINS-32412) Build should fail if upload failed
Title: Message Title Magnus Reftel commented on JENKINS-32412 Re: Build should fail if upload failed Same thing happens when the site cannot be found. We got "Not publishing because no Confluence Site could be found. Check your Confluence configuration in system settings.", and the build succeeded. It would have been nice if it had failed the build, so that we could have fixed the problem right then. Now we discovered by coincidence much later that the pages had not been published for quite a while. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.167530.1452603649000.4003.1564490220308%40Atlassian.JIRA.
[JIRA] (JENKINS-58730) [FUTURE] Add http url variable to GitLabSCMSource
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58730 [FUTURE] Add http url variable to GitLabSCMSource Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-07-30 12:33 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda See https://github.com/jenkinsci/gitlab-branch-source-plugin/pull/14#discussion_r308589411 Add Comment
[JIRA] (JENKINS-58729) Extended security settings plugin cannot be configured
Title: Message Title Pierre Laroche created an issue Jenkins / JENKINS-58729 Extended security settings plugin cannot be configured Issue Type: Bug Assignee: Matt Sicker Components: paranoia-plugin Created: 2019-07-30 12:31 Environment: Jenkins version : 2.176.2 LTS. Extended security plugin version : 1.0 Priority: Major Reporter: Pierre Laroche Hello. I have just installed the extended-security-settings plugin. When I open the Global Security page, the following stack trace is displayed. org.apache.commons.jelly.JellyTagException: jar:file:/data/rec/melusine/6599_jenkins_ACT210/war/WEB-INF/lib/jenkins-core-2.176.2.jar!/lib/layout/layout.jelly:266:25: org.apache.commons.jelly.JellyTagException: jar:file:/data/rec/melusine/6599_jenkins_ACT210/war/WEB-INF/lib/jenkins-core-2.176.2.jar!/lib/layout/main-panel.jelly:36:21: org.apache.commons.jelly.JellyTagException: jar:file:/data/rec/melusine/6599_jenkins_ACT210/war/WEB-INF/lib/jenkins-core-2.176.2.jar!/lib/form/form.jelly:58:22: org.apache.commons.jelly.JellyTagException: jar:file:/data/rec/melusine/6599_jenkins_ACT210/war/WEB-INF/lib/jenkins-core-2.176.2.jar!/lib/form/rowSet.jelly:47:23: org.apache.commons.jelly.JellyTagException: No page found 'config.jelly' for class io.jenkins.plugins.extendedsecuritysettings.ExtendedSecuritySettings at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] (JENKINS-58513) Flake in RestartPipelineTest#terminatedPodAfterRestart
Title: Message Title Jesse Glick commented on JENKINS-58513 Re: Flake in RestartPipelineTest#terminatedPodAfterRestart kubernetes #561 removed the failing assertion. Still need to track down the reason. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200657.156327728.3997.1564489860137%40Atlassian.JIRA.
[JIRA] (JENKINS-58728) Skip rerunning tests on release
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-58728 Skip rerunning tests on release Issue Type: Task Assignee: Jesse Glick Components: bom Created: 2019-07-30 12:22 Priority: Minor Reporter: Jesse Glick Try adding to the parent: skip-tests-on-release performRelease true true Add Comment
[JIRA] (JENKINS-58726) Possibility to set build display name with the ${releaseVersion}
Title: Message Title
JEROME ARNAL closed an issue as Won't Do
Jenkins / JENKINS-58726
Possibility to set build display name with the ${releaseVersion}
Change By:
JEROME ARNAL
Status:
Open Closed
Resolution:
Won't Do
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201019.1564480007000.3940.1564486980093%40Atlassian.JIRA.
[JIRA] (JENKINS-58726) Possibility to set build display name with the ${releaseVersion}
Title: Message Title
JEROME ARNAL commented on JENKINS-58726
Re: Possibility to set build display name with the ${releaseVersion}
C'est en fait déjà possible avec la variable : MVN_RELEASE_VERSION
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201019.1564480007000.3939.1564486920046%40Atlassian.JIRA.
[JIRA] (JENKINS-58727) Misleading log message when no e-mail is sent
Title: Message Title Carlos Garcia updated an issue Jenkins / JENKINS-58727 Misleading log message when no e-mail is sent Change By: Carlos Garcia Summary: Mailer refuses to send Misleading log message when no e-mail from post >> cleanup is sent Issue Type: Bug Improvement Priority: Major Trivial Given the attached Groovy pipeline script (irrelevant parts removed), mailer plugin complais with the following error message: No mail will be sent out, as 'XXX' does not have a result yet. Please make sure you set a proper result in case of pipeline/build scripts. It complains even though the build result is SUCCESS.It worked several days ago, before an update of Jenkins and certain plugins.+ Is there anybody experiencing a similar issue? Maybe there is something wrong in my script, but it worked before, during months.If there is any workaround to avoid this, it will be welcome :) EDIT: When no e-mail has to be sent, a misleading message is printed in build log. I would not consider this a bug, but removing this message (or changing its text) would be an improvement :) Add Comment
[JIRA] (JENKINS-58705) Change default working dir to /home/jenkins/agent
Title: Message Title Vincent Latombe updated JENKINS-58705 Jenkins / JENKINS-58705 Change default working dir to /home/jenkins/agent Change By: Vincent Latombe Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200995.1564403053000.3934.1564485660345%40Atlassian.JIRA.
[JIRA] (JENKINS-58705) Change default working dir to /home/jenkins/agent
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-58705 Change default working dir to /home/jenkins/agent Change By: Vincent Latombe Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200995.1564403053000.3932.1564485600414%40Atlassian.JIRA.
[JIRA] (JENKINS-50218) Conan init fails when using Artifactory plugin
Title: Message Title Javier G. Sogo commented on JENKINS-50218 Re: Conan init fails when using Artifactory plugin Hi! I've just submitted a PR that could fix this issue: https://github.com/jfrog/jenkins-artifactory-plugin/pull/178. Thanks for the feedback! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189242.152120704.3927.1564485600338%40Atlassian.JIRA.
[JIRA] (JENKINS-58727) Mailer refuses to send e-mail from post >> cleanup
Title: Message Title Carlos Garcia edited a comment on JENKINS-58727 Re: Mailer refuses to send e-mail from post >> cleanup It seems to be only a misleading log message coming from mailer plugin.When the plugin is expected to send an e-mail (i.e: the build fails, or changes to normal after a failure), the log is not printed out and the e-mail is sent. When the build was SUCCESS and it is SUCCESS again, no e-mail is expected to be sent, and no e-mail is sent, but this log appears.It is safe to simply ignore the message. EDIT: Please, you can close the issue :) And sorry for the alarm. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201021.1564483585000.3924.1564485420102%40Atlassian.JIRA.
[JIRA] (JENKINS-58727) Mailer refuses to send e-mail from post >> cleanup
Title: Message Title Carlos Garcia commented on JENKINS-58727 Re: Mailer refuses to send e-mail from post >> cleanup It seems to be only a misleading log message coming from mailer plugin. When the plugin is expected to send an e-mail (i.e: the build fails, or changes to normal after a failure), the log is not printed out and the e-mail is sent. When the build was SUCCESS and it is SUCCESS again, no e-mail is expected to be sent, and no e-mail is sent, but this log appears. It is safe to simply ignore the message. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201021.1564483585000.3922.1564485300108%40Atlassian.JIRA.
[JIRA] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Title: Message Title Andrew Dean commented on JENKINS-18162 Re: Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects I'm getting this issue with up to date plugins and it is 2019... I have an upstream job calling a downstream one and it occasionally figures out what to do with parameters but other times it pretends like they don't exist and executes anyway. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.149460.1370020502000.3915.1564483980314%40Atlassian.JIRA.
[JIRA] (JENKINS-58724) Add a log to know wich Run is executed on a pod
Title: Message Title Vincent Latombe updated JENKINS-58724 Jenkins / JENKINS-58724 Add a log to know wich Run is executed on a pod Change By: Vincent Latombe Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201017.1564478302000.3912.1564483921317%40Atlassian.JIRA.
[JIRA] (JENKINS-58727) Mailer refuses to send e-mail from post >> cleanup
Title: Message Title Carlos Garcia updated an issue Jenkins / JENKINS-58727 Mailer refuses to send e-mail from post >> cleanup Change By: Carlos Garcia Given the attached Groovy pipeline script (irrelevant parts removed), mailer plugin complais with the following error message: No mail will be sent out, as ' V6_Interfaces » DK_AC_WIFI_1_2G » BUILD_DK_AC_WIFI_1_2G_DEV #1 XXX ' does not have a result yet. Please make sure you set a proper result in case of pipeline/build scripts.It complains even though the build result is SUCCESS.It worked several days ago, before an update of Jenkins and certain plugins.+ Is there anybody experiencing a similar issue? Maybe there is something wrong in my script, but it worked before, during months.If there is any workaround to avoid this, it will be welcome :) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201021.1564483585000.3910.1564483680161%40Atlassian.JIRA.
[JIRA] (JENKINS-58727) Mailer refuses to send e-mail from post >> cleanup
Title: Message Title Carlos Garcia created an issue Jenkins / JENKINS-58727 Mailer refuses to send e-mail from post >> cleanup Issue Type: Bug Assignee: Adrien Lecharpentier Attachments: build.groovy.txt Components: mailer-plugin Created: 2019-07-30 10:46 Environment: mailer 1.24, Jenkins 2.176.2 Priority: Major Reporter: Carlos Garcia Given the attached Groovy pipeline script (irrelevant parts removed), mailer plugin complais with the following error message: No mail will be sent out, as 'V6_Interfaces » DK_AC_WIFI_1_2G » BUILD_DK_AC_WIFI_1_2G_DEV #1' does not have a result yet. Please make sure you set a proper result in case of pipeline/build scripts. It complains even though the build result is SUCCESS. It worked several days ago, before an update of Jenkins and certain plugins.+ Is there anybody experiencing a similar issue? Maybe there is something wrong in my script, but it worked before, during months. If there is any workaround to avoid this, it will be welcome
[JIRA] (JENKINS-58724) Add a log to know wich Run is executed on a pod
Title: Message Title Mathieu Delrocq updated an issue Jenkins / JENKINS-58724 Add a log to know wich Run is executed on a pod Change By: Mathieu Delrocq In my our company, we have a large service to perform integration tasks for many applications.For concern of invoicing the resources used on our infrastructure, we need to know what job is running on a pod with kubernetes-plugin.Firstly, I purpose to add a LOGGER to know, like docker-plugin do, wich task is being accepted or was completed on an agent. I'm listening if you have any suggest or others solutions to perform it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201017.1564478302000.3897.1564480920062%40Atlassian.JIRA.
[JIRA] (JENKINS-58724) Add a log to know wich Run is executed on a pod
Title: Message Title Mathieu Delrocq updated an issue Jenkins / JENKINS-58724 Add a log to know wich Run is executed on a pod Change By: Mathieu Delrocq In my company, we have a large service to perform integration tasks for many applications.For concern of invoicing every ressources the resources used on our infrastructure , we need to know what job is running on a pod with kubernetes-plugin.Firstly, I purpose to add a LOGGER to know, like docker-plugin do, wich task is being accepted or was completed on an agent. I'm listening if you have any suggest or an other way others solutions to perform it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201017.1564478302000.3896.1564480860061%40Atlassian.JIRA.
[JIRA] (JENKINS-58724) Add a log to know wich Run is executed on a pod
Title: Message Title Mathieu Delrocq updated an issue Jenkins / JENKINS-58724 Add a log to know wich Run is executed on a pod Change By: Mathieu Delrocq We In my company, we have a large service to perform integration tasks for many applications.For concern of invoicing every ressources used, we need to know what job is running on a pod with kubernetes-plugin . For this reason Firstly , I purpose to add a LOGGER to know , like docker-plugin do, wich task is being accepted , or was completed on an agent. I'm listening if you have any suggest or an other way to perform it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201017.1564478302000.3895.1564480560079%40Atlassian.JIRA.
[JIRA] (JENKINS-58724) Add a log to know wich Run is executed on a pod
Title: Message Title Mathieu Delrocq commented on JENKINS-58724 Re: Add a log to know wich Run is executed on a pod Pull Request submitted : pull 562 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201017.1564478302000.3894.1564480140158%40Atlassian.JIRA.
[JIRA] (JENKINS-58377) Add instructions for multibranch pipeline jobs
Title: Message Title Parichay Barpanda updated JENKINS-58377 Jenkins / JENKINS-58377 Add instructions for multibranch pipeline jobs Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200498.1562590092000.3892.1564480020138%40Atlassian.JIRA.
[JIRA] (JENKINS-58726) Possibility to set build display name with the ${releaseVersion}
Title: Message Title
JEROME ARNAL created an issue
Jenkins / JENKINS-58726
Possibility to set build display name with the ${releaseVersion}
Issue Type:
Task
Assignee:
Unassigned
Components:
maven-plugin
Created:
2019-07-30 09:46
Priority:
Minor
Reporter:
JEROME ARNAL
It would be nice if we can use ${releaseVersion} to change the build display name or the build description. When i Try this i Have : Failed to evaluate description Failed to evaluate name macro:org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Unrecognized macro 'releaseVersion' in '${releaseVersion}'
Add Comment
[JIRA] (JENKINS-58725) Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending.
Title: Message Title fen zhou updated an issue Jenkins / JENKINS-58725 Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending. Change By: fen zhou !https://wiki.yitu-inc.com/download/attachments/440928856/image2019-5-27_20-8-27.png?version=1=1558958907248=v2! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201018.1564479331000.3891.1564479420152%40Atlassian.JIRA.
[JIRA] (JENKINS-58725) Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter job will all be pending.
Title: Message Title fen zhou created an issue Jenkins / JENKINS-58725 Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter job will all be pending. Issue Type: Bug Assignee: John Westcott Components: ansible-tower-plugin Created: 2019-07-30 09:35 Labels: plugin ansible-plugin ansible tower awx Priority: Major Reporter: fen zhou Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-58725) Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending.
Title: Message Title fen zhou updated an issue Jenkins / JENKINS-58725 Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending. Change By: fen zhou Summary: Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter job jobs will all be pending. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201018.1564479331000.3889.1564479360256%40Atlassian.JIRA.
[JIRA] (JENKINS-58724) Add a log to know wich Run is executed on a pod
Title: Message Title Mathieu Delrocq updated an issue Jenkins / JENKINS-58724 Add a log to know wich Run is executed on a pod Change By: Mathieu Delrocq Issue Type: Task New Feature Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201017.1564478302000.3885.1564478400120%40Atlassian.JIRA.
[JIRA] (JENKINS-58724) Add a log to know wich Run is executed on a pod
Title: Message Title Mathieu Delrocq created an issue Jenkins / JENKINS-58724 Add a log to know wich Run is executed on a pod Issue Type: Task Assignee: Mathieu Delrocq Components: kubernetes-plugin Created: 2019-07-30 09:18 Priority: Minor Reporter: Mathieu Delrocq We need to know what job is running on a pod. For this reason, I purpose to add a LOGGER to know wich task is being accepted, or was completed on an agent. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-58597) Additional Step error with message
Title: Message Title ethorsa commented on JENKINS-58597 Re: Additional Step error with message I have implemented a prototype of a new step. If there's interest I can contribute it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200755.1563785676000.3883.1564476600147%40Atlassian.JIRA.
[JIRA] (JENKINS-58672) Stop installing Oracle JDK 6 when there is no Java found on the agent
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-58672 Stop installing Oracle JDK 6 when there is no Java found on the agent Change By: Baptiste Mathus Labels: java11 triaged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200954.1564131287000.3882.1564475520331%40Atlassian.JIRA.
[JIRA] (JENKINS-58394) Passwords are not masked in Maven multi-module downstream jobs
Title: Message Title Jeroen Laverman commented on JENKINS-58394 Re: Passwords are not masked in Maven multi-module downstream jobs Is there any progress on this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200519.1562652326000.3879.1564474740282%40Atlassian.JIRA.
[JIRA] (JENKINS-58722) Invalid ssh remote url
Title: Message Title Parichay Barpanda updated JENKINS-58722 Jenkins / JENKINS-58722 Invalid ssh remote url Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201014.1564470656000.3877.1564474200084%40Atlassian.JIRA.
[JIRA] (JENKINS-58723) Make Folder Authorization Strategy Immutable
Title: Message Title Abhyudaya Sharma updated an issue Jenkins / JENKINS-58723 Make Folder Authorization Strategy Immutable Change By: Abhyudaya Sharma Labels: gsoc-2019 Sprint: GSoC 2019. Coding Phase 3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201016.1564473649000.3873.1564473720142%40Atlassian.JIRA.
