[JIRA] (JENKINS-57902) Multiple upstream job triggers for downstream job triggers only old build instead of triggering latest build
Title: Message Title ratna polepalli created an issue Jenkins / JENKINS-57902 Multiple upstream job triggers for downstream job triggers only old build instead of triggering latest build Issue Type: Bug Assignee: Unassigned Attachments: not_latest_build.png Components: other Created: 2019-06-07 04:46 Priority: Critical Reporter: ratna polepalli We have a job which builds the image. --> BUILD_JOB We have another job that will trigger based on the build job, if it is successful then this job will trigger --> TEST_EXECUTION_JOB. Now in TEST_EXECUTION_JOB --> A build runs and in execution. Now in Queue there are 2 builds --> B and C. After A builds Completes , It should pick the latest build C , but Jenkins is picking the build B(which is OLD compared to Build C). I hope I explained correctly. Attached the screenshot which facing issue in my jenkins job In attached screenshot 2 builds came (i.e 858 and 859) 858 is old and 859 is latest. But my jenkins job is taking 858 to run instead of taking 859. Please provide the solution that something jenkins team to work or I need to modify something in my groovy code.
[JIRA] (JENKINS-57622) Community Bounding Phase for Cloud features for EWM GSoC 2019
Title: Message Title Yufei Zhang resolved as Done Jenkins / JENKINS-57622 Community Bounding Phase for Cloud features for EWM GSoC 2019 Change By: Yufei Zhang Status: In Progress 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.199551.1558579622000.23140.1559877420127%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57679) Implement AwsEfsDisk class and rewrite Disk class as base class
Title: Message Title Yufei Zhang stopped work on JENKINS-57679 Change By: Yufei Zhang Status: In Progress Open 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.199614.1558759056000.23141.1559877420156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57680) Design the clouds package to support AWS related method call
Title: Message Title Yufei Zhang updated an issue Jenkins / JENKINS-57680 Design the clouds package to support AWS related method call Change By: Yufei Zhang Sprint: GSoC 2019. Coding Phase 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.199615.1558759197000.23139.1559877360292%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57680) Design the clouds package to support AWS related method call
Title: Message Title Yufei Zhang updated an issue Jenkins / JENKINS-57680 Design the clouds package to support AWS related method call Change By: Yufei Zhang Sprint: GSoC 2019. Coding Phase 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.199615.1558759197000.23138.1559877360205%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title CJ Harmath commented on JENKINS-53188 Re: New jobs created from Blue Ocean are tied with username that created them This is how my job's config.xml starts '1.1' encoding='UTF-8'?> "workflow-multibranch@2.21"> test rest.impl.pipeline.credential.BlueOceanCredentialsProvider_-FolderPropertyImpl plugin="blueocean-pipeline-scm-api@1.14.0"> "credentials@2.1.19"> blueocean-folder-credential-domain Blue Ocean Folder Credentials domain testuser github-enterprise:bd08318e10264d38792523a9e76b6f818f8ec73616f7b13b99692ed940ce642c rest.impl.pipeline.credential.BlueOceanCredentialsProvider_-FolderPropertyImpl> "pipeline-model-definition@1.3.8"> "docker-commons@1.14"/> And I wonder if the BlueOceanCredentialProvider which references the testuser's credential can be changed to use the global credential instead. I already have a jenkins level github enterprise access token credential, so i would like to just use that. That token btw was issued to a service account which is also added on the GitHub Enterprise side with a nice Jenkins icon, so it looks much better than the pipeline creator's photo next to a Pull request check. I've just changed the testuser to jenkins user then updated the user level credential as well and it works, but it's hacky and too involved. 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-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title CJ Harmath commented on JENKINS-53188 Re: New jobs created from Blue Ocean are tied with username that created them I've stumbled up this as I was curious how to setup a pipeline with a global credential instead of a user specific. Currently when a user creates a new pipeline at first time, he/she will be asked for a personal access token for github which then gets stored in the users credential. Since users can come and go, it would be more practical if an administrator can set the credential. This also has an added value of GitHub checks not showing the user who created the pipeline, but the user configured by the admin. Happy to submit a new issue. Thanks, CJ 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.193214.1534948736000.23134.1559875380213%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51641) Duplicate commits displayed on Pipeline build when using "Poll SCM" and "Pipeline script from SCM"
Title: Message Title Jack Bradach commented on JENKINS-51641 Re: Duplicate commits displayed on Pipeline build when using "Poll SCM" and "Pipeline script from SCM" Funny you should ask; turns out the affected jobs all run a script that does one or more perforce checkouts as part of the build process as some sort of Uzumaki in Makefile form. >.< They're going to make it stop doing that, and I imagine we'll be fine until it awakens again. 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.191054.1527786048000.23130.1559873040310%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55088) Jenkins Home config.xml reset upon restart
Title: Message Title Brijesh Trivedi commented on JENKINS-55088 Re: Jenkins Home config.xml reset upon restart We are having the same issue. Jenkins Version: `2.164.3` and using `google auth`. Every time I restart Jenkins the config.xml is overwritten. Also Jenkins on AWS, EBS backed volume. Michael Schneider did you found any solution or workaround? 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.196141.1544218094000.23122.1559868670153%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55088) Jenkins Home config.xml reset upon restart
Title: Message Title Brijesh Trivedi commented on JENKINS-55088 Re: Jenkins Home config.xml reset upon restart We are having the same issue. Jenkins Version: `2.164.3` and using `google auth`. Every time I restart Jenkins the config.xml is overwritten. Also Jenkins on AWS, EBS backed volume. Michael Schneider did you found any solution or workaround? 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.196141.1544218094000.23127.1559868720018%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57901) Concurrent Pipeline builds report all changes since last completed build
Title: Message Title William Brode created an issue Jenkins / JENKINS-57901 Concurrent Pipeline builds report all changes since last completed build Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-06-07 00:21 Environment: Jenkins ver. 2.164.3 p4-plugin 1.9.6 Priority: Minor Reporter: William Brode When running two concurrent pipeline builds, the second one will contain the changes from the first (so long as the first hasn't finished running when the second pipeline starts). CL 1 starts a build CL 2 starts a build Then Build #2 will contain CL 1 and CL 2 even though it is really only "newly" building CL 2. This causes issues for reporting (e-mails, jenkins ui, ect) since it makes it look like CL 1 was first introduced in Build #2 when it was really introduced in Build #1. Add Comment
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Jason MCDev commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head Any movement here or additional information that I can provide? We are seeing this error multiple times a day. 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.196374.1545361815000.23106.1559866860336%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51641) Duplicate commits displayed on Pipeline build when using "Poll SCM" and "Pipeline script from SCM"
Title: Message Title William Brode commented on JENKINS-51641 Re: Duplicate commits displayed on Pipeline build when using "Poll SCM" and "Pipeline script from SCM" When I've seen this before it's because we are doing the same checkout multiple times. Are you sure your checkout wasn't inside of a loop or something? Or are your source and jenkinsfile and pipeline shared library all on the same perforce server? 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.191054.1527786048000.23103.1559866202228%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57830) Better default for PodTemplateStep.label
Title: Message Title
Jesse Glick edited a comment on JENKINS-57830
Re: Better default for PodTemplateStep.label
{{BUILD_TAG}} will not work, however, in cases where the job name is not a label K8s label. Thus [this defaulting|https://github.com/jenkinsci/kubernetes-plugin/blob/fd3953c85aaa2d3c731e6e5fe4e0e25688ad5673/src/main/java/org/csanchez/jenkins/plugins/kubernetes/pipeline/PodTemplateStep.java#L66] needs to use something like [this|https://github.com/jenkins-x/jx-java-client/blob/4909b74d9ff02db999be0689a84956af1bcee5ab/src/main/java/io/jenkins/x/client/kube/KubernetesNames.java#L8-L45], or perhaps simpler since the {{name}} could be any random string (it already gets [uniquified|https://github.com/jenkinsci/kubernetes-plugin/blob/fd3953c85aaa2d3c731e6e5fe4e0e25688ad5673/src/main/java/org/csanchez/jenkins/plugins/kubernetes/pipeline/PodTemplateStepExecution.java#L76-L79]) so long as it bears some resemblance to the job name.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199786.155961517.23100.1559865660130%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57886) Add JCasC config test
Title: Message Title Parichay Barpanda updated JENKINS-57886 Jenkins / JENKINS-57886 Add JCasC config test 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.199850.1559832725000.23098.1559865300263%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57900) Add loggers to GitLabServer and GitLabServers
Title: Message Title Parichay Barpanda updated JENKINS-57900 Jenkins / JENKINS-57900 Add loggers to GitLabServer and GitLabServers 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.199865.1559856482000.23095.1559863800161%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57892) Remove synchronisation of GitLabServers methods
Title: Message Title Parichay Barpanda updated JENKINS-57892 Jenkins / JENKINS-57892 Remove synchronisation of GitLabServers methods 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.199856.155984465.23096.1559863800191%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57894) Move parameters from databoundconstructor to databoundsetters
Title: Message Title Parichay Barpanda updated JENKINS-57894 Jenkins / JENKINS-57894 Move parameters from databoundconstructor to databoundsetters 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.199858.1559846169000.23094.1559863740117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57900) Add loggers to GitLabServer and GitLabServers
Title: Message Title Parichay Barpanda updated JENKINS-57900 Jenkins / JENKINS-57900 Add loggers to GitLabServer and GitLabServers 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.199865.1559856482000.23093.1559861340075%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57900) Add loggers to GitLabServer and GitLabServers
Title: Message Title Parichay Barpanda started work on JENKINS-57900 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.199865.1559856482000.23092.1559861220068%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57892) Remove synchronisation of GitLabServers methods
Title: Message Title Parichay Barpanda updated JENKINS-57892 Jenkins / JENKINS-57892 Remove synchronisation of GitLabServers methods 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.199856.155984465.23091.1559860680106%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57892) Remove synchronisation of GitLabServers methods
Title: Message Title Parichay Barpanda started work on JENKINS-57892 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.199856.155984465.23090.1559860500187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56082) Merge yaml from parent pod template
Title: Message Title Jesse Glick commented on JENKINS-56082 Re: Merge yaml from parent pod template Both PRs have now been merged, so should this be closed? 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.197509.154988034.23086.1559858820176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57317) Exception when checking 'Validate S3 Bucket configuration'
Title: Message Title Jesse Glick commented on JENKINS-57317 Re: Exception when checking 'Validate S3 Bucket configuration' I tried using the Evergreen instructions but they failed in EC2EvergreenInstance: The specified instance type can only be used in a VPC. A subnet ID or network interface ID is required to carry out the request. (Service: AmazonEC2; Status Code: 400; Error Code: VPCResourceNotSpecified; Request ID: …) 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.199086.1556866104000.23083.1559857200232%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57900) Add loggers to GitLabServer and GitLabServers
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57900 Add loggers to GitLabServer and GitLabServers Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-06-06 21:28 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Add this member instance to the GitLabServer Class private static final Logger LOGGER = LoggerFactory.getLogger(GitLabServer.class); And to GitLabServers Class private static final Logger LOGGER = LoggerFactory.getLogger(GitLabServers.class);
[JIRA] (JENKINS-57894) Move parameters from databoundconstructor to databoundsetters
Title: Message Title Parichay Barpanda updated JENKINS-57894 Jenkins / JENKINS-57894 Move parameters from databoundconstructor to databoundsetters 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.199858.1559846169000.23080.1559856300082%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57894) Move parameters from databoundconstructor to databoundsetters
Title: Message Title Parichay Barpanda started work on JENKINS-57894 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.199858.1559846169000.23079.1559855220400%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57884) Add a more specific authentication matcher
Title: Message Title Parichay Barpanda updated JENKINS-57884 Remove the API models for authentication Jenkins / JENKINS-57884 Add a more specific authentication matcher 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.199848.155983152.23078.1559855220335%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57805) Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Title: Message Title Jesse Glick commented on JENKINS-57805 Re: Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance Well you can try. 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.199756.1559335134000.23077.1559853420111%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57899) Jira site configuration lost after a reboot
Title: Message Title Daniel Beland updated an issue Jenkins / JENKINS-57899 Jira site configuration lost after a reboot Change By: Daniel Beland Environment: jira-plugin 3.0.7 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.199864.1559853126000.23075.1559853240058%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57899) Jira site configuration lost after a reboot
Title: Message Title Daniel Beland created an issue Jenkins / JENKINS-57899 Jira site configuration lost after a reboot Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2019-06-06 20:32 Priority: Critical Reporter: Daniel Beland I configured my Jira site using the latest plugin version 3.0.7 All worked fine (recognised the issue in my scm comment and added a link to Jira) However after a reboot I noticed the configuration was lost, also I couldn't find any configuration file in my jenkins home directory. I downgraded the plugin to version 3.0.6 and now I can see the file hudson.plugins.jira.JiraProjectProperty.xml is created when I add a Jira site. If I update the plugin back to the latest version 3.0.7 and modify the configuration, the content of the file is lost. Add Comment
[JIRA] (JENKINS-57805) Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Title: Message Title Devin Nusbaum commented on JENKINS-57805 Re: Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance Thanks, I filed https://github.com/jenkinsci/workflow-api-plugin/pull/94 to harden bruteForceScanForEnclosingBlock. Halting execution if there is a problem in the node graph seems reasonable to me Ok, and you think it makes sense to do this from `CpsFlowExecution.getNode`, so that that method would no longer throw exceptions and would instead terminate the program and return null if loading the node returns an error? 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.199756.1559335134000.23072.1559852640183%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57898) Write unit tests for implemented functions
Title: Message Title Long Nguyen updated an issue Jenkins / JENKINS-57898 Write unit tests for implemented functions Change By: Long Nguyen Issue Type: Task Improvement 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.23054.1559851440087%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57550) bitbucket single sign on account credentials not recognized
Title: Message Title Chanakya Mathi closed an issue as Not A Defect Jenkins / JENKINS-57550 bitbucket single sign on account credentials not recognized Change By: Chanakya Mathi Status: Open Closed Resolution: Not A Defect 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.199459.1558332961000.23051.1559851380815%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57898) Write unit tests for implemented functions
Title: Message Title Long Nguyen created an issue Jenkins / JENKINS-57898 Write unit tests for implemented functions Issue Type: Task Assignee: Long Nguyen Components: remoting-kafka-plugin Created: 2019-06-06 20:02 Labels: gsoc-2019 Priority: Major Reporter: Long Nguyen 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
[JIRA] (JENKINS-57896) Launching Zookeeper and Kafka in K8s Function
Title: Message Title Long Nguyen started work on JENKINS-57896 Change By: Long Nguyen 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.199860.1559851236000.23050.1559851380805%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57897) Update diagrams and docs for Phase 1
Title: Message Title Long Nguyen created an issue Jenkins / JENKINS-57897 Update diagrams and docs for Phase 1 Issue Type: Task Assignee: Long Nguyen Components: remoting-kafka-plugin Created: 2019-06-06 20:01 Labels: gsoc-2019 Priority: Major Reporter: Long Nguyen 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
[JIRA] (JENKINS-57896) Launching Zookeeper and Kafka in K8s Function
Title: Message Title Long Nguyen created an issue Jenkins / JENKINS-57896 Launching Zookeeper and Kafka in K8s Function Issue Type: New Feature Assignee: Long Nguyen Components: remoting-kafka-plugin Created: 2019-06-06 20:00 Labels: gsoc-2019 Priority: Major Reporter: Long Nguyen 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
[JIRA] (JENKINS-57667) Launching Zookeeper and Kafka in K8s UI
Title: Message Title Long Nguyen updated an issue Jenkins / JENKINS-57667 Launching Zookeeper and Kafka in K8s UI Change By: Long Nguyen Summary: Launching Zookeeper and Kafka in K8s UI 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.199600.155871834.23037.1559851080072%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57886) Add JCasC config test
Title: Message Title Parichay Barpanda started work on JENKINS-57886 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.199850.1559832725000.23034.1559850900199%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57884) Add a more specific authentication matcher
Title: Message Title Parichay Barpanda updated JENKINS-57884 Jenkins / JENKINS-57884 Add a more specific authentication matcher 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.199848.155983152.23033.1559850900172%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57886) Add JCasC config test
Title: Message Title Parichay Barpanda assigned an issue to Joseph Petersen Jenkins / JENKINS-57886 Add JCasC config test Change By: Parichay Barpanda Assignee: Parichay Barpanda Joseph Petersen 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.199850.1559832725000.23036.1559850900236%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57884) Add a more specific authentication matcher
Title: Message Title Parichay Barpanda commented on JENKINS-57884 Re: Add a more specific authentication matcher Ongoing work with some other changes can be followed here - https://github.com/baymac/gitlab-branch-source-plugin/pull/6 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.199848.155983152.23018.1559850420043%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57502) Cmake arguments sometimes are added to path in parallel build
Title: Message Title Martin Weber updated an issue Jenkins / JENKINS-57502 Cmake arguments sometimes are added to path in parallel build Change By: Martin Weber Priority: Blocker Minor 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.199365.1557999255000.22964.1559847720124%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57895) Enable/Disable Job via REST redirects after succeeding causing 403
Title: Message Title James VanderZouwen commented on JENKINS-57895 Re: Enable/Disable Job via REST redirects after succeeding causing 403 I should mention that we do not enforce CSRF tokens 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.199859.1559847216000.22962.1559847300039%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57895) Enable/Disable Job via REST redirects after succeeding causing 403
Title: Message Title
James VanderZouwen created an issue
Jenkins / JENKINS-57895
Enable/Disable Job via REST redirects after succeeding causing 403
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2019-06-06 18:53
Environment:
Jenkins 2.173
Labels:
jenkins
Priority:
Minor
Reporter:
James VanderZouwen
Using powershell, you can easily reproduce this. assumptions: anonymous access is completely disabled $theCredentials = "user:USERTOKEN"; $basicAuth = "Basic " + [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes($theCredentials)) $headers = @ { "Authorization" = $basicAuth } Invoke-WebRequest -Method "Post" -Uri "http://jenkinsstaging.mycompany.com:8000/job/COMPILE_CHANGE-2297/enable" -Headers $headers This works, but then the call is redirected to the issue page without the auth headers - causing a 403 unauthorized. This should respond with a 200
[JIRA] (JENKINS-57894) Move parameters from databoundconstructor to databoundsetters
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57894 Move parameters from databoundconstructor to databoundsetters Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-06-06 18:36 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda In order to be flexible with change in signature, see https://github.com/baymac/gitlab-branch-source-plugin/pull/5#discussion_r291315338 Add Comment
[JIRA] (JENKINS-56922) FolderConfigFileAction.doShow NullPointerException
Title: Message Title Vladimir Kulev commented on JENKINS-56922 Re: FolderConfigFileAction.doShow NullPointerException Here are my steps to reproduce: open some job and click "Pipeline Syntax" (/job/.../pipeline-syntax/ URL) select "configFileProvider" step and some file click "view selected file" 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.198599.155456968.22948.1559845980115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57893) Mask Kubernetes secrets bound to containers in build log
Title: Message Title Jesse Glick updated JENKINS-57893 Jenkins / JENKINS-57893 Mask Kubernetes secrets bound to containers in build log Change By: Jesse Glick 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.199857.1559845148000.22946.1559845920110%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57893) Mask Kubernetes secrets bound to containers in build log
Title: Message Title Jesse Glick started work on JENKINS-57893 Change By: Jesse Glick 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.199857.1559845148000.22940.1559845200279%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57893) Mask Kubernetes secrets bound to containers in build log
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-57893 Mask Kubernetes secrets bound to containers in build log Issue Type: New Feature Assignee: Jesse Glick Components: kubernetes-plugin Created: 2019-06-06 18:19 Labels: security Priority: Major Reporter: Jesse Glick If you bind Kubernetes secrets to environment variables, and the values of secrets are printed by some process running in the pod, the text should be masked from the build log to prevent accidental disclosure. This is analogous to the masking behavior performed by the withCredentials step. Add Comment
[JIRA] (JENKINS-57892) Remove synchronisation of GitLabServers methods
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57892 Remove synchronisation of GitLabServers methods Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-06-06 18:10 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda As discussed with Justin Harringa and Jeff Pearce, see https://github.com/baymac/gitlab-branch-source-plugin/pull/5#discussion_r291194839 Add Comment
[JIRA] (JENKINS-57862) A wrong configuration of CasC yaml kill Jenkins startup
Title: Message Title Ramon Leon commented on JENKINS-57862 Re: A wrong configuration of CasC yaml kill Jenkins startup Also if the yaml file is removed you have to edit io.jenkins.plugins.casc.CasCGlobalConfig.xml to remove the file. 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.199824.1559748979000.22888.1559843280161%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50711) plugin doesn't work with ssh link to git repo
Title: Message Title John Elion edited a comment on JENKINS-50711 Re: plugin doesn't work with ssh link to git repo Discovered by accident: If I create a copy of a job that has this bug, the copy does not seem to! (Click "New Item" in a folder, give the new item a name and choose "Copy" down at the bottom, and enter the name of the job that is breaking like this.) Save, run the job once (the first time it has been working for everybody), run it again - and the second time seems to be working. Even after doing this, the original job still has the error described by this bug.I looked at the two config.xml files - they seem identical except for a GUID. So I'm not sure why this happens, but it might provide a sort of workaround to those who are frustrated by this behavior.My jobs are all FreeStyle jobs. I have seen this on multiple jobs (I had to essentially rename a bunch of jobs because their common suffix was part of an exclusion pattern in a test config.). I am confident that, because it is still happening on the original jobs, it is not related to any sort of plugin upgrades (I have upgraded plugins, though the Git plugins I noted above are still at those same versions.) 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.189802.1523350889000.22855.1559841360330%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50711) plugin doesn't work with ssh link to git repo
Title: Message Title John Elion commented on JENKINS-50711 Re: plugin doesn't work with ssh link to git repo Discovered by accident: If I create a copy of a job that has this bug, the copy does not seem to! (Click "New Item" in a folder, give the new item a name and choose "Copy" down at the bottom, and enter the name of the job that is breaking like this.) Save, run the job once (the first time it has been working for everybody), run it again - and the second time seems to be working. Even after doing this, the original job still has the error described by this bug. I looked at the two config.xml files - they seem identical except for a GUID. So I'm not sure why this happens, but it might provide a sort of workaround to those who are frustrated by this behavior. My jobs are all FreeStyle jobs. 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.189802.1523350889000.22848.1559841240216%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56825) Don't redact URL in support-core anonymization
Title: Message Title John C Bland II commented on JENKINS-56825 Re: Don't redact URL in support-core anonymization Arnaud Héritier as a user, it makes the links in the emails useless. We cannot visit the links because they're broken. 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.198481.1554062136000.22836.1559839800298%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51791) git polling fails to detect changes when build uses multiple repos
Title: Message Title Jeff Smick commented on JENKINS-51791 Re: git polling fails to detect changes when build uses multiple repos We're seeing this, too. The polling log seems to indicate that the first repository is the only one used to trigger the build. However, the first repo for us is our shared libraries repo. 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.191239.1528398073000.22827.1559839680205%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57891) FileCopyOperation does not work from outside the workspace
Title: Message Title Nicolas Boussuge created an issue Jenkins / JENKINS-57891 FileCopyOperation does not work from outside the workspace Issue Type: Bug Assignee: Suresh Kumar Components: file-operations-plugin Created: 2019-06-06 16:39 Priority: Minor Reporter: Nicolas Boussuge FolderCopyOperation relies on hudson.FilePath#FilePath(hudson.FilePath, java.lang.String), with the first argument being the workspace and the second the user provided string. This implementation handles properly relative / absolute paths. FileCopyOperation relies on hudson.FilePath#list(java.lang.String, java.lang.String), with both arguments being provided by the user (includes & excludes). This implementation treats the input as an Ant GLOB pattern, and does not support absolute paths. Since it is possible to copy any directory from anywhere, it should be possible to copy files from outside the current workspace. Maybe something like an optional parameter "sourceFileLocation". Add Comment
[JIRA] (JENKINS-57225) Remove the GIT SCM configuration prerequisites
Title: Message Title Jose Then edited a comment on JENKINS-57225 Re: Remove the GIT SCM configuration prerequisites I agree this would be a great improvement. I am currently hitting this need when trying to configure a scripted pipeline with the Kubernetes Plugin. I am trying to get a list of Tags before I clone within one of my pods. 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.198983.1556555313000.22823.1559838780294%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57225) Remove the GIT SCM configuration prerequisites
Title: Message Title Jose Then commented on JENKINS-57225 Re: Remove the GIT SCM configuration prerequisites I agree this would be a great improvement. I am currently hitting this need when trying to configure a scripted pipeline with the Kubernetes Plugin. I am trying to get a list of Tags before I clone within one of my pods. 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.198983.1556555313000.22820.1559838780257%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57890) FileDownloadOperation sometimes fails without user/password
Title: Message Title Nicolas Boussuge created an issue Jenkins / JENKINS-57890 FileDownloadOperation sometimes fails without user/password Issue Type: Bug Assignee: Suresh Kumar Components: file-operations-plugin Created: 2019-06-06 16:23 Priority: Minor Reporter: Nicolas Boussuge The problem is as stated on the title. After debug, it appears this is fixed by the [following commit|https://github.com/jenkinsci/file-operations-plugin/commit/da1c222a1f59368624ac1f24494d893127646ab2]: Replace string comparison using '==' There has been no release since the fix, 15 months ago. For now, we have to use this workaround, which, I assume, relies on downloading the file from the master before serializing the content to the slave: writeFile file: 'myfile', text: 'url'.toURL().text Add Comment
[JIRA] (JENKINS-57884) Add a more specific authentication matcher
Title: Message Title Parichay Barpanda started work on JENKINS-57884 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.199848.155983152.22815.1559838180066%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57883) [FUTURE] Remove gitlab server name from user view
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57883 [FUTURE] Remove gitlab server name from user view Change By: Parichay Barpanda Summary: [FUTURE] Remove gitlab server name from user view 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.199846.1559830741000.22812.1559837940117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57754) [FUTURE] Advanced button should align with delete button
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57754 [FUTURE] Advanced button should align with delete button Change By: Parichay Barpanda Summary: [FUTURE] Advanced button should align with delete button 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.199699.1559162932000.22813.1559837940144%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57889) Add HashTable or HashMap for GitLabServer faster access
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57889 Add HashTable or HashMap for GitLabServer faster access Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-06-06 16:16 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda See https://github.com/baymac/gitlab-branch-source-plugin/pull/5#discussion_r291257804 Add Comment
[JIRA] (JENKINS-56825) Don't redact URL in support-core anonymization
Title: Message Title Arnaud Héritier commented on JENKINS-56825 Re: Don't redact URL in support-core anonymization I don't disagree Ryan Campbell I think this need is really rare while it's very painful on the support side. My problem remains that the anonymization is very aggressive today and not at all configurable (it's white or black) 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.198481.1554062136000.22808.1559836620273%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57686) Add Java 8 functional interfaces for behavioural design pattern
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57686 Add Java 8 functional interfaces for behavioural design pattern Change By: Parichay Barpanda Issue Type: Improvement Story 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.199621.1558824827000.22804.1559836200293%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57686) Add Java 8 functional interfaces for behavioural design pattern
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57686 Add Java 8 functional interfaces for behavioural design pattern Change By: Parichay Barpanda Component/s: gitlab-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.199621.1558824827000.22805.1559836200344%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title
Gavin Williams updated an issue
Jenkins / JENKINS-57888
Custom log format broken by 2.177
Change By:
Gavin Williams
Upon upgrading from 2.176 to 2.177, it would appear that support for providing a custom log format has been broken, due to what looks like an undocumented [ change | ( [https://github.com/jenkinsci/winstone/pull/63] ] ) in the Winstone library. Logging.properties file:{code:java}.level=ALLhandlers=java.util.logging.ConsoleHandlerjava.util.logging.SimpleFormatter.format=[%1$tF %1$tT.%1$tL][%4$s][%2$s] %5$s %6$s%n java.util.logging.ConsoleHandler.level=INFO java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter{code}I've also added the following JVM argument:{code:java}-Djava.util.logging.config.file=/var/lib/jenkins/logging.properties{code} Log format with 2.176:{noformat}[2019-06-06 15:10:07.881][INFO][jenkins.InitReactorRunner$1 onAttained] Completed initialization[2019-06-06 15:10:08.052][INFO][hudson.WebAppMain$3 run] Jenkins is fully up and running{noformat} Log format with 2.177:{noformat}2019-06-06 15:11:40.956+ [id=29] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization 2019-06-06 15:11:41.136+ [id=20] INFO hudson.WebAppMain$3#run: Jenkins is fully up and running{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title
Gavin Williams updated an issue
Jenkins / JENKINS-57888
Custom log format broken by 2.177
Change By:
Gavin Williams
Upon upgrading from 2.176 to 2.177, it would appear that support for providing a custom log format has been broken, I suspect by due to what looks like an undocumented [change|[https://github.com/jenkinsci/winstone/pull/63]] in the upgrade of Jetty Winstone library . Logging.properties file:{code:java}.level=ALLhandlers=java.util.logging.ConsoleHandlerjava.util.logging.SimpleFormatter.format=[%1$tF %1$tT.%1$tL][%4$s][%2$s] %5$s %6$s%n java.util.logging.ConsoleHandler.level=INFO java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter{code}I've also added the following JVM argument:{code:java}-Djava.util.logging.config.file=/var/lib/jenkins/logging.properties{code} Log format with 2.176:{noformat}[2019-06-06 15:10:07.881][INFO][jenkins.InitReactorRunner$1 onAttained] Completed initialization[2019-06-06 15:10:08.052][INFO][hudson.WebAppMain$3 run] Jenkins is fully up and running{noformat} Log format with 2.177:{noformat}2019-06-06 15:11:40.956+ [id=29] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization 2019-06-06 15:11:41.136+ [id=20] INFO hudson.WebAppMain$3#run: Jenkins is fully up and running{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Gavin Williams created an issue Jenkins / JENKINS-57888 Custom log format broken by 2.177 Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-06-06 15:23 Priority: Major Reporter: Gavin Williams Upon upgrading from 2.176 to 2.177, it would appear that support for providing a custom log format has been broken, I suspect by the upgrade of Jetty. Logging.properties file: .level=ALL handlers=java.util.logging.ConsoleHandler java.util.logging.SimpleFormatter.format=[%1$tF %1$tT.%1$tL][%4$s][%2$s] %5$s %6$s%n java.util.logging.ConsoleHandler.level=INFO java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter I've also added the following JVM argument: -Djava.util.logging.config.file=/var/lib/jenkins/logging.properties Log format with 2.176: [2019-06-06 15:10:07.881][INFO][jenkins.InitReactorRunner$1 onAttained] Completed initialization [2019-06-06 15:10:08.052][INFO][hudson.WebAppMain$3 run] Jenkins is fully up and running Log format with 2.177:
[JIRA] (JENKINS-57515) AIX slave start error due to can not found /com/sun/jna/aix-ppc64/libjnidispatch.so
Title: Message Title Markus Winter commented on JENKINS-57515 Re: AIX slave start error due to can not found /com/sun/jna/aix-ppc64/libjnidispatch.so I have the same issue. So I opened a pull request https://github.com/jenkinsci/jenkins/pull/4060 that will update the JNA library to 5.3.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.199418.1558076672000.22798.1559833920181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57833) All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-57833
Re: All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log
> But why is "source not found" the expected behavoir? shouldn't there be a valid class loaded?"source not found" means that it is provided by the JVM jar(s) directly and this is what we desire. Sometimes, it's an old/outdated XML parsing implementation that it loaded and you get a source such as ".../xercesImpl-2.6.2.jar". It is often caused by plugins forgetting to exclude old versions of Xerces from their dependencies. > openjdk version "1.8.0_212"This is a JDK that works well. The problem is likely to be a plugin that pull an outdated version of XercesImpl {noformat}class org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -> file:/var/jenkins_home/plugins/registry_reporter/WEB-INF/lib/xercesImpl-2.6.2.jar{noformat}https://issues.jenkins-ci.org/browse/JENKINS-47486?focusedCommentId=318000=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-318000
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.199790.1559631863000.22795.1559833740306%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38893) Active Choice Reactive Reference parameter value rendered as File Selector not cascaded
Title: Message Title Sunil Batra commented on JENKINS-38893 Re: Active Choice Reactive Reference parameter value rendered as File Selector not cascaded The issue mentioned Ioannis Moutsatsos is there, but I could add another finding, when we use the same active choice in pipeline job, the file is not uploaded either you specify OR In Pipeline type of job, you can get the name of the file, but do not have a space where the file could be located. 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.175304.1476186813000.22793.1559833740230%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57833) All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log
Title: Message Title Cyrille Le Clerc commented on JENKINS-57833 Re: All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log > But why is "source not found" the expected behavoir? shouldn't there be a valid class loaded? "source not found" means that it is provided by the JVM jar(s) directly and this is what we desire. Sometimes, it's an old/outdated XML parsing implementation that it loaded and you get a source such as ".../xercesImpl-2.6.2.jar". It is often caused by plugins forgetting to exclude old versions of Xerces from their dependencies. class org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -> file:/var/jenkins_home/plugins/registry_reporter/WEB-INF/lib/xercesImpl-2.6.2.jar https://issues.jenkins-ci.org/browse/JENKINS-47486?focusedCommentId=318000=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-318000 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.199790.1559631863000.22789.1559833680128%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57833) All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log
Title: Message Title Markus Till edited a comment on JENKINS-57833 Re: All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log the one bundeld with the offical docker image openjdk version "1.8.0_212"OpenJDK Runtime Environment (build 1.8.0_212-b04)OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode) 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.199790.1559631863000.22774.1559833260112%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57833) All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log
Title: Message Title Markus Till commented on JENKINS-57833 Re: All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log the one bundeld with the offical docker image 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.199790.1559631863000.22772.1559833200213%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57833) All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log
Title: Message Title Markus Till commented on JENKINS-57833 Re: All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log seems adding the -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl to the JAVA_OPTS seem to work. But I'm still confused why this is needed. 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.199790.1559631863000.22768.1559833140130%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57887) Merge existing users
Title: Message Title James Howe created an issue Jenkins / JENKINS-57887 Merge existing users Issue Type: Improvement Assignee: Nicolas Bachschmidt Components: additional-identities-plugin Created: 2019-06-06 14:56 Priority: Minor Reporter: James Howe Multiple users for the same person have already been created (one login, one scm). Configuring additional identities for the login user to add the scm id doesn't appear to have any effect - both the separate users still appear on the People page. Are there additional steps that should be taken, or is this just not possible? Add Comment
[JIRA] (JENKINS-57886) Add JCasC config test
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57886 Add JCasC config test Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-06-06 14:52 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Based on suggestion of Joseph Petersen (https://github.com/baymac/gitlab-branch-source-plugin/pull/5#issuecomment-499515653), Will add more details after some research and discussions. Add Comment
[JIRA] (JENKINS-42179) withMaven doesn't discover the released artifacts when executing "mvn release"
Title: Message Title Robin Jansohn commented on JENKINS-42179 Re: withMaven doesn't discover the released artifacts when executing "mvn release" Is there any way to suppress this output? One of our tests starts a separate java process and expects no output to appear... 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.179061.148752434.22762.1559832300133%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57885) Moved GitLabServer filters from serverUrl to name
Title: Message Title Parichay Barpanda resolved as Fixed Jenkins / JENKINS-57885 Moved GitLabServer filters from serverUrl to name Change By: Parichay Barpanda Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199849.1559831935000.22759.1559832000107%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57885) Moved GitLabServer filters from serverUrl to name
Title: Message Title Parichay Barpanda commented on JENKINS-57885 Re: Moved GitLabServer filters from serverUrl to name See https://github.com/baymac/gitlab-branch-source-plugin/pull/4#discussion_r291188583 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.199849.1559831935000.22760.1559832000136%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57885) Moved GitLabServer filters from serverUrl to name
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57885 Moved GitLabServer filters from serverUrl to name Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-06-06 14:38 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Moved the gitlabserver filter methods like addServer, updateServer, removeServer etc to check the server based on it's name rather than it's serverUrl which was the case previously. Add Comment
[JIRA] (JENKINS-57884) Add a more specific authentication matcher
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57884 Add a more specific authentication matcher Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-06-06 14:32 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda See https://github.com/baymac/gitlab-branch-source-plugin/pull/4/files/50cae4a7994d035e45fccdcf93b715641b6f270a#r291186646 Add Comment
[JIRA] (JENKINS-10258) Allow users unicity
Title: Message Title James Howe updated an issue Jenkins / JENKINS-10258 Allow users unicity Change By: James Howe Component/s: additional-identities-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.140446.1310133744000.22726.1559831401080%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52418) While adding new slave via Launch slave agent via ssh not able to select the via drop down existing credentials or new credentials which we have added recently
Title: Message Title James Howe commented on JENKINS-52418 Re: While adding new slave via Launch slave agent via ssh not able to select the via drop down existing credentials or new credentials which we have added recently I don't think this as anything to do with the Additional Identities 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.192215.1530960754000.22719.1559831220150%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57883) Remove gitlab server name from user view
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57883 Remove gitlab server name from user view Issue Type: Story Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-06-06 14:19 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Based on the comment of Jeff Pearce https://github.com/baymac/gitlab-branch-source-plugin/pull/5#discussion_r291190882 , If the user never requires to have a use case for knowing the internal name for gitlab server then remove it from view. This can be implemented in future. Add Comment
[JIRA] (JENKINS-57751) Unable to delete server configuration
Title: Message Title
Parichay Barpanda updated JENKINS-57751
This issue was solved by modifying the `configure` method of Global configuration. Before:
@Override
public boolean configure(StaplerRequest req, JSONObject json) throws FormException {
req.bindJSON(this, json);
return true;
}
After:
@Override
public boolean configure(StaplerRequest req, JSONObject json) throws FormException {
servers = req.bindJSONToList(GitLabServer.class, json.get("servers"));
save();
return super.configure(req, json);
}
The servers arraylist is updated with changes in Global Configuration UI.
Jenkins / JENKINS-57751
Unable to delete server configuration
Change By:
Parichay Barpanda
Status:
In Review Resolved
Resolution:
Fixed
Add Comment
[JIRA] (JENKINS-57833) All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log
Title: Message Title Cyrille Le Clerc commented on JENKINS-57833 Re: All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log Which jvm version are you using? 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.199790.1559631863000.22714.1559829420120%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50176) Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks
Title: Message Title Christopher Head commented on JENKINS-50176 Re: Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks There is a workaround (of sorts) which we deployed in our environment (we are using a declarative pipeline): put a loop around the lock statement which breaks out only once the variable is set successfully. It means you lose the FIFO property, and occasionally it can deadlock if there are a lot of waiters, but in a low-contention case the waiter will loop and on the second iteration the lock will be free so it will get it and set the variable. 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.189195.1521053055000.22688.1559829300605%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57880) Check if gitlab server name is unique
Title: Message Title Parichay Barpanda closed an issue as Fixed This issue has been resolved by adding a default unique value to GitLabServer expecting that user doesn't change it. See https://github.com/baymac/gitlab-branch-source-plugin/pull/5 Jenkins / JENKINS-57880 Check if gitlab server name is unique Change By: Parichay Barpanda Status: In Progress 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.199843.1559821791000.22686.1559828400232%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57833) All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log
Title: Message Title Markus Till commented on JENKINS-57833 Re: All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log I don't really get how to resolve this. Should I add -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl to the starting Jenkins Process or to the maven run? 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.199790.1559631863000.22684.1559827860109%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57833) All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log
Title: Message Title Markus Till commented on JENKINS-57833 Re: All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log I get the following output. But why is "source not found" the expected behavoir? shouldn't there be a valid class loaded? DocumentBuilderFactory: com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl@57dc5f4f class com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl -> source not found 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.199790.1559631863000.22681.1559827560119%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57882) junit Test Result Age shows next build number
Title: Message Title Steve Graham created an issue Jenkins / JENKINS-57882 junit Test Result Age shows next build number Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 2019-06-06 13:17 Environment: jenkins 2.179 junit plugin 1.28 linux, running behind apache server Labels: regression Priority: Minor Reporter: Steve Graham Test results are being processed with the jUnit plugin ( latest version ) The age displayed in the results shows the next build number Test Duration Age myTest 0 ms 1035 and the specific test results are: Failing for the past 1,035 builds (Since #0 ) This was build #1034, the next build will be #1035 In the previous build the test was Skipped #1032 Passed #1033 Skipped for the past 1,034 builds (Since #0 ) #1034 Failing for the past 1,035 builds (Since #0 ) Possible Regression or Feature - I have never seen this before
[JIRA] (JENKINS-57880) Check if gitlab server name is unique
Title: Message Title Parichay Barpanda started work on JENKINS-57880 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.199843.1559821791000.22678.1559827020237%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56925) extra newline character from powershell output
Title: Message Title gek commented on JENKINS-56925 Re: extra newline character from powershell output But how? Only way i see is use Write-Host -NoNewline , but it's output cannot be passed throw: https://serverfault.com/questions/859826/output-is-truncated-in-jenkins-job-when-launching-powershell-script-remotely-usi For some reason Write-Host -NoNewline output cannot be assigned to variable. 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.198603.1554635511000.22674.1559826240708%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57857) Dashboard - 'Select subset of tools' not working
Title: Message Title Ulli Hafner commented on JENKINS-57857 Re: Dashboard - 'Select subset of tools' not working I think it would make sense to wait a couple of days to have some meaningful data for the chart. 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.199818.1559728494000.22673.1559826240366%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57433) Seed Job - Picks up incorrect Boolean Operator Classes
Title: Message Title
Daniel Spilker updated JENKINS-57433
You can not arbitrarily mix built-in and dynamic DSL. Use the API viewer to lookup the syntax.
job('example-1') {
steps {
singleConditionalBuilder {
condition {
and {
conditions {
conditionContainer {
condition {
statusCondition {
bestResult('FAILURE')
worstResult('ABORTED')
}
}
}
conditionContainer {
condition {
not {
condition {
fileExistsCondition {
baseDir {
workspace()
}
file('script.sh')
}
}
}
}
}
}
}
}
runner {
fail()
}
buildStep {
shell {
command('echo Hello World')
}
}
}
}
}job('example-2') {
steps {
conditionalSteps {
condition {
and {
status('ABORTED', 'FAILURE')
} {
not {
fileExists('script.sh', BaseDir.WORKSPACE)
}
}
}
runner('Fail')
steps {
shell {
command('echo Hello World')
}
}
}
}
}
Jenkins / JENKINS-57433
Seed Job - Picks up incorrect Boolean Operator Classes
Change By:
Daniel Spilker
Status:
Open Fixed but Unreleased
Resolution:
Not A Defect
Add
[JIRA] (JENKINS-50176) Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks
Title: Message Title Carlos Garcia commented on JENKINS-50176 Re: Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks The same issue is reproduced in my environment. Does anybody know if there is a feasible solution? Is there any release planned to address this issue? 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.189195.1521053055000.22642.1559825280820%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
