[JIRA] (JENKINS-36543) Boolean input parameter ignores default value of false
Title: Message Title Hendrik Brinkmann updated an issue Jenkins / JENKINS-36543 Boolean input parameter ignores default value of false Change By: Hendrik Brinkmann Attachment: checkbox.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Tom FENNELLY commented on JENKINS-38079 Re: Investigate performance degradation report Yeah, this is strange for sure from an SSE configure pov because the cost of what it is doing should be constant and small i.e. it is not searching anything or moving data around. I will look into this too from an SSE pov, but one thing I plan for this is to make the configure process completely async + remove all locking on the request path. Of course that will only have a limited effect if it's a case that the host is starved of threads from the request thread pool because of other long-running requests. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Denys Digtiar assigned an issue to Unassigned Jenkins / JENKINS-37289 authentication issue instant is too old or in the future Change By: Denys Digtiar Assignee: Ben McCann Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38228) Incorrect implementation of `loadUserByUsename`, Users are added on demand
Title: Message Title Denys Digtiar created an issue Jenkins / JENKINS-38228 Incorrect implementation of `loadUserByUsename`, Users are added on demand Issue Type: Bug Assignee: Unassigned Components: saml-plugin Created: 2016/Sep/15 7:27 AM Environment: Jenkins Docker 2.7.4-alpine saml-plugin 0.6 Priority: Major Reporter: Denys Digtiar Steps to reproduce: 1. Setup the SAML Security Realm 2. Switch to any of the Matrix Authorization strategies 3. Add a random string of characters as users Expected Users mark with appropriate icon as non-existent (i.e. crossed out, icon with a cross) Actual User are added to the Jenkins, see People to confirm. Add Comment
[JIRA] (JENKINS-37710) Can't connect to TFS with TFS-PLUGIN
Title: Message Title Laura Molero commented on JENKINS-37710 Re: Can't connect to TFS with TFS-PLUGIN Thank you very much! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38205) Failed to deploy war on Weblogic: task completed abnormally (exit code = 1)
Title: Message Title Raphael CHAUMIER commented on JENKINS-38205 Re: Failed to deploy war on Weblogic: task completed abnormally (exit code = 1) Your weblogic doesn't need to be on the jenkins machine. This is possible but not necessary. If you don't set an additional classpath the plugin try to find out a weblogic installation on the same machine. Do you have a master/slaves jenkins architecture ? Is your job run on the master or a slave ? Concerning the field validation this is a bug which will be fixed in the next release. Regards, Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35476) Pipeline projects are not listed in widget
Title: Message Title Ignacio Albors resolved as Fixed Resolved in the master branch. To be released a new version soon Jenkins / JENKINS-35476 Pipeline projects are not listed in widget Change By: Ignacio Albors Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-38226) Collapsible View to show only favourites
Title: Message Title Darragh Sherwin created an issue Jenkins / JENKINS-38226 Collapsible View to show only favourites Issue Type: New Feature Assignee: Unassigned Components: blueocean-plugin Created: 2016/Sep/15 6:06 AM Priority: Minor Reporter: Darragh Sherwin It would nice if we could collapse the view to hide away all jobs and the header bar and only show favourites for a more "radiator view", something similar to the Radiator View Plugin Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-36543) Boolean input parameter ignores default value of false
Title: Message Title Hendrik Brinkmann commented on JENKINS-36543 Re: Boolean input parameter ignores default value of false I use Jenkins ver. 2.7.4 LTS and face the same issue. If I try def deploy = input message: 'Deploy released version to alpha? ', parameters: [booleanParam(defaultValue: false, description: '', name: 'DEPLOY')] the Checkbox is always checked true (see also my screenshot among the attachements). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38229) jenkins master not executing jobs on master and slaves and just stalls saying "Waiting for next available executor"
Title: Message Title Arun V created an issue Jenkins / JENKINS-38229 jenkins master not executing jobs on master and slaves and just stalls saying "Waiting for next available executor" Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Sep/15 7:38 AM Environment: x86_64 GNU/Linux box, jenkins version:1.642.2 Priority: Critical Reporter: Arun V Our jenkins machine has few linux slaves and aws nodes connected to it. All of sudden no jobs get executed and everything is stuck as "Waiting for next available executor" The labels are fine and executors exist but we still get the same issue. This happens for jobs on both master and slave executors. Pasting the stack trace. Let us know if you need more information. Thanks Sep 15, 2016 12:22:17 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: item.getCauseOfBlockage() in /job/job-name/buildHistory/ajax. Reason: java.lang.NullPointerException java.lang.NullPointerException Sep 15, 2016 12:22:18 AM hudson.triggers.SafeTimerTask run SEVERE: Timer task hudson.model.Queue$MaintainTask@53dd07f5 failed java.lang.NullPointerException Sep 15, 2016 12:22:20 AM hudson.triggers.SafeTimerTask run SEVERE: Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@1a5b4113 failed java.lang.NullPointerException Sep 15, 2016 12:22:20 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: item.isStuck() in /ajaxBuildQueue. Reason: java.lang.NullPointerException java.lang.NullPointerException Sep 15, 2016 12:22:20 AM hudson.ExpressionFactory2$JexlExpression
[JIRA] (JENKINS-38034) SAML Plugin does not load groups when access with API Token
Title: Message Title Denys Digtiar updated an issue Jenkins / JENKINS-38034 SAML Plugin does not load groups when access with API Token Change By: Denys Digtiar Labels: SAML2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38228) Incorrect implementation of `loadUserByUsename`, Users are added on demand
Title: Message Title Denys Digtiar updated an issue Jenkins / JENKINS-38228 Incorrect implementation of `loadUserByUsename`, Users are added on demand Change By: Denys Digtiar Labels: SAML2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38231) Role-Strategy Macro page should not display class names by default
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-38231 Role-Strategy Macro page should not display class names by default Issue Type: Improvement Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2016/Sep/15 7:54 AM Priority: Minor Reporter: Oleg Nenashev This information is useful for troubleshooting only, but it consumes too much space Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-21475) Multiple LDAP OU support
Title: Message Title Greg Staniak edited a comment on JENKINS-21475 Re: Multiple LDAP OU support +1 for this. Right now we've got to allow our "human users" OU foe for people to get their work done, bur the single OU condition means problems when we need a more "service" account for any reason (like an account dedicated to automation, used only with an API token from scripts). This is a really painful limitation. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30840) "possible next launch" view column
Title: Message Title Ignacio Albors commented on JENKINS-30840 Re: "possible next launch" view column I think the second column could be too confusing. Probably I will add only another column type with the possible next launch, just like the widgets: keep both concepts independents. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38019) Pipeline Job:Integration with MongoDB required
Title: Message Title kishorerp commented on JENKINS-38019 Re: Pipeline Job:Integration with MongoDB required Correct. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12163) Cleaning VM before start next job in queue.
Title: Message Title Oren Chapo reopened an issue Unfortunately, this doesn't work for pipeline jobs. If I set "Disconnect After Limited Builds" value to 1, the "What to do when the slave is disconnected" action never happens. It seems like "part of *" pipeline jobs that run on slaves are not detected as real jobs. I suspect this because "build history" is empty for a node that only runs parts of pipeline jobs. The outcome is inability to ensure each test starts with a clean (from snapshot) VM. If other "part of" jobs are queued for the node, they will start running the moment a previous (partial) job finishes. I've tried the suggested workarounds, but ended up either breaking the queued job (which starts with "dirty" machine, or breaks because the VM stops after the job started running) or breaking the current job (which gets stuck because I shutdown the slave before the job is finished). Jenkins / JENKINS-12163 Cleaning VM before start next job in queue. Change By: Oren Chapo Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37710) Can't connect to TFS with TFS-PLUGIN
Title: Message Title Laura Molero edited a comment on JENKINS-37710 Re: Can't connect to TFS with TFS-PLUGIN Thank you very much!Now it works. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37770) Malformed JSON for /blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject
Title: Message Title emanuelez commented on JENKINS-37770 Re: Malformed JSON for /blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject I'm using an old version of the plugin (0.17) so that might be it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38230) Role-Strategy Macro page escapes extension documentation
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38230 Role-Strategy Macro page escapes extension documentation Change By: Oleg Nenashev Summary: Role-Strategy Macro page escapes extension documentation Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38230) Role-Strategy Macro page escapes extension documentation
Title: Message Title Oleg Nenashev started work on JENKINS-38230 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38225) TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD)
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-38225 TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD) Change By: GMC Software Development B Corporate I have tested the tokengroups group-lookup strategy of the (newest) Active Directory Plugin in our AD-environment. Our AD is setup as forest, were some users are located in the root-domain (e.g., root.local), but most user-accounts, security-groups and computers are located in the second resource-domain (e.g., subx.local).Therefore, the plugin is currently configured with* Domain Name = "subx.local,root.local",* Domain controller = "dc1.subx.local:3268,dc2.subx.local:3268"* Group Membership Lookup Strategy = "RECURSIVE"With this configuration, login "against" a local group of subx.local by using an account of root.local (which is member of the local group) is permitted.If I change the the group-lookup strategy to "TOKENGROUPS", the login fails *) .. and after some tests (with logging 'FINE'), I've determined (or assume), that:* Searching for the user-object and login (with credentials) is successful,* also getting the tokengroups-list (SIDs) will contain local, universal groups of the subx.local (which DC was asked),* But the the name-translation of the tokengroups-SIDs afterwards, is limited to the domain (by Bind-DN) of the user-object. Therefore, the security-groups of our resource-domain (subx.local) were not found! *) More concrete:Login with an account of the resource-domain (subx.local) is still successful; an much faster.The failure/problem occurs only with accounts of the "extra" root-domain. Assuming, that my findings/assumptions are correct: It is possible to change the implementation, that groups of "different" (but also configured/permitted domain), are permitted?Best regards from Salzburg,Markus Add Comment
[JIRA] (JENKINS-35476) Pipeline projects are not listed in widget
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35476 Re: Pipeline projects are not listed in widget Code changed in jenkins User: Ignacio Albors Path: src/main/java/hudson/plugins/nextexecutions/NextBuilds.java src/main/java/hudson/plugins/nextexecutions/NextExecutionsWidget.java src/main/java/hudson/plugins/nextexecutions/columns/NextExecutionColumn.java src/main/java/hudson/plugins/nextexecutions/utils/NextExecutionsUtils.java http://jenkins-ci.org/commit/next-executions-plugin/f67fb0dbbb86e269a1728070360f4a4526b1b125 Log: Consider everything that has triggers as parameter. Take into account not only AbstractProject but everything that implements ParameterizedJobMixIn.ParameterizedJob.class. Thus Pipeline jobs will be also considered (see JENKINS-35476) Compare: https://github.com/jenkinsci/next-executions-plugin/compare/7caa8d4d31b7...f67fb0dbbb86 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23606) Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits
Title: Message Title Souciance Eqdam Rashti commented on JENKINS-23606 Re: Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits We are seeing the same issue here. We have set included and excluded regions but merge commits trigger all jobs which causes some jobs to fail and we have to manually trigger them. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30840) "possible next launch" view column
Title: Message Title Ignacio Albors edited a comment on JENKINS-30840 Re: "possible next launch" view column I think the second column could be too confusing.Probably I will add only another column type with the possible next launch, just like the widgets: keep both concepts independents independent . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26907) HockeyApp Configuration Lost after Jenkins Restart
Title: Message Title Darragh Sherwin assigned an issue to Oliver H Hi Oliver, Can you please look into my pull request ? Thanks Darragh Jenkins / JENKINS-26907 HockeyApp Configuration Lost after Jenkins Restart Change By: Darragh Sherwin Assignee: Darragh Sherwin Oliver H Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36210) expose details through REST API
Title: Message Title Ignacio Albors assigned an issue to Ignacio Albors Jenkins / JENKINS-36210 expose details through REST API Change By: Ignacio Albors Assignee: Ignacio Albors Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38219) Restrict Job.CONFIGURE permissions by plugins
Title: Message Title ikedam commented on JENKINS-38219 Re: Restrict Job.CONFIGURE permissions by plugins Macro supports in role-strategy-plugin might be helpful for this feature. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30840) "possible next launch" view column
Title: Message Title Ignacio Albors resolved as Fixed Done. It will be included in the next release. Jenkins / JENKINS-30840 "possible next launch" view column Change By: Ignacio Albors Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38257) Feature to define non-actual user
Title: Message Title ikedam created an issue Jenkins / JENKINS-38257 Feature to define non-actual user Issue Type: New Feature Assignee: ikedam Components: authorize-project-plugin, core Created: 2016/Sep/15 8:41 PM Priority: Minor Reporter: ikedam Authorize-project plugin has difficulties for its usage as it requires actual users to run builds as. It can easily conflicts with policies of administrators: Administrators might don't want to use an actual user for managing authorizations of builds. E.g. Alice and Bob belongs to a DevOps team. They want to run a project with the authorization of DevOps, but not of Alice or Bob. Because it might cause problems when they quit the job. This can be resolved by defining a non-actual user used only to manage authorizations of builds. Administrator doesn't want to define or can't define non-actual users. It can be the case especialy when they use an external authentication system (such as Active Directory). This can be resolved by introducing a feature to define non-actual users, just like build-in users such as ANONYMOUS and SYSTEM. They cannot be used to login Jenkins. (They don't have passwords)
[JIRA] (JENKINS-37791) When running a pipeline from a favourite we should not move the card
Title: Message Title Cliff Meyers commented on JENKINS-37791 Re: When running a pipeline from a favourite we should not move the card I had to do a bunch of cleanup to the Favorites Cards now that the new Capabilities API is in place; decided to impl this too at the same time and found a solution I like that didn't require a huge amount of code to do this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37791) When running a pipeline from a favourite we should not move the card
Title: Message Title Cliff Meyers commented on JENKINS-37791 Re: When running a pipeline from a favourite we should not move the card PR: https://github.com/jenkinsci/blueocean-plugin/pull/502 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37791) When running a pipeline from a favourite we should not move the card
Title: Message Title Cliff Meyers updated JENKINS-37791 Jenkins / JENKINS-37791 When running a pipeline from a favourite we should not move the card Change By: Cliff Meyers Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Title: Message Title
Mark Waite edited a comment on JENKINS-33984
Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Yes, you would need to specify multiple refspecs behind the advanced button of the repository definition for the job. I assume your {noformat}origin/release**{noformat} branch specifier really means { { noformat} origin/release/** {noformat } }: . I think your refspec should look like this: {noformat}+refs/heads/develop:refs/remotes/origin/develop+refs/heads/release/*:refs/remotes/origin/release/*{noformat}The [git refspecs documentation|https://git-scm.com/book/en/v2/Git-Internals-The-Refspec] gives a very good review of the strengths and weaknesses of refspec definition.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30840) "possible next launch" view column
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30840 Re: "possible next launch" view column Code changed in jenkins User: Ignacio Albors Path: src/main/java/hudson/plugins/nextexecutions/columns/NextExecutionColumn.java src/main/java/hudson/plugins/nextexecutions/columns/PossibleNextExecutionColumn.java src/main/java/hudson/plugins/nextexecutions/utils/NextExecutionsUtils.java src/main/resources/hudson/plugins/nextexecutions/columns/Messages.properties http://jenkins-ci.org/commit/next-executions-plugin/fea6f926d4743aa194311c6fc6a5f7a64841bee0 Log: Added a column type with the next possible builds. It shows when the next scm polling will be done. If there is any scm change a new build will be launch. Fixes JENKINS-30840 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38217) Roadmap of authorize-project-plugin
Title: Message Title
ikedam updated an issue
Jenkins / JENKINS-38217
Roadmap of authorize-project-plugin
Change By:
ikedam
authorize-project-plugin have following issues for its design.* Authentications of the project during configuration and after configuration may change.** This makes it difficult for other plugins behave depending on authentications of projects.* The way to reject unauthenticated configurations is unstable.** authorize-project plugin should reject user A configure a project when the project is configured as user B.** The current implementation raises exception when saving unauthenticated configurfation.* Difficult to configure permissions of builds.** What users really want to do is to configure permissions of builds.*** This is why I named it "authorize-project".** {{QueueItemAuthenticator}} is designed to return {{Authentication}}, which can be considered a user.** And then, the current design of authorize-project is to configure builds run as a specific user.*** This might mean "authenticate-project" was more appropreate for the plugin name.** This causes following difficulties:*** There can be cases that administrators don't want to bind a project to an actual specific user. Alice and Bob belongs to DevOps group. They want run builds of a project as the permission of DevOps, but don't to run as Alice or Bob as they both want configure the project.*** There can be cases that administrators cannot define a new user for build authentications. E.g. Jenkins is configured to use an external user dictionary (e.g. Active Directory) and the administrator of Jenkins doesn't administer that directory.|| Issue || Resolution || JIRA ticket ||| Authentication may change when configuration | Split configuration page | JENKINS-35081 || Unstable way to reject unauthenticated configuration | Restrict CONFIGURE permission by plugins | JENKINS-38219 || Difficulties in configuring permissions | Introduce define additional build-in users | JENKINS-38257 |
Add Comment
[JIRA] (JENKINS-38258) covcomplplot-plugin unnecessarily depends on Subversion
Title: Message Title Dmitry Erastov created an issue Jenkins / JENKINS-38258 covcomplplot-plugin unnecessarily depends on Subversion Issue Type: Bug Assignee: Unassigned Components: covcomplplot-plugin Created: 2016/Sep/15 9:40 PM Environment: Jenkins 2.22 Coverage/Complexity Scatter Plot PlugIn 1.1.1 Labels: subversion dependencies plugin coverage Priority: Minor Reporter: Dmitry Erastov I'd like to disable the Subversion plugin in my Jenkins installation, and the only plugin that's consuming it right now is the Coverage/Complexity Scatter Plot. I'm not an expert on how Jenkins plugins work, but it seems the sole reason for this is that the plugin's pom.xml [references](https://github.com/jenkinsci/covcomplplot-plugin/blob/master/pom.xml#L40) an old svn repo for Powermock. This has since moved to Github, so it would seem that the repo URL needs to be updated (or removed, if the library is available from the core Jenkins repo). I didn't find any other references to Subversion in the plugin's source code. Can someone confirm this analysis?
[JIRA] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Title: Message Title
Mark Waite edited a comment on JENKINS-33984
Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Yes, you would need to specify multiple refspecs behind the advanced button of the repository definition for the job. I assume your ` {{ origin/release** ` }} branch specifier really means ` {{ origin/release/** ` }} :{noformat}+refs/heads/develop:refs/remotes/origin/develop+refs/heads/release/*:refs/remotes/origin/release/*{noformat}The [git refspecs documentation|https://git-scm.com/book/en/v2/Git-Internals-The-Refspec] gives a very good review of the strengths and weaknesses of refspec definition.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Title: Message Title
Mark Waite edited a comment on JENKINS-33984
Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Yes, you would need to specify multiple refspecs behind the advanced button of the repository definition for the job. I assume your { { noformat} origin/release** {noformat } } branch specifier really means {{origin/release/**}}:{noformat}+refs/heads/develop:refs/remotes/origin/develop+refs/heads/release/*:refs/remotes/origin/release/*{noformat}The [git refspecs documentation|https://git-scm.com/book/en/v2/Git-Internals-The-Refspec] gives a very good review of the strengths and weaknesses of refspec definition.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Title: Message Title Mark Waite commented on JENKINS-33984 Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1) Yes, you would need to specify multiple refspecs behind the advanced button of the repository definition for the job. I assume your `origin/release*` branch specifier really means `origin/release/*`: +refs/heads/develop:refs/remotes/origin/develop +refs/heads/release/*:refs/remotes/origin/release/* The git refspecs documentation gives a very good review of the strengths and weaknesses of refspec definition. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38258) covcomplplot-plugin unnecessarily depends on Subversion
Title: Message Title Dmitry Erastov updated an issue Jenkins / JENKINS-38258 covcomplplot-plugin unnecessarily depends on Subversion Change By: Dmitry Erastov I'd like to disable the Subversion plugin in my Jenkins installation, and the only plugin that's consuming it right now is the Coverage/Complexity Scatter Plot.I'm not an expert on how Jenkins plugins work, but it seems the sole reason for this is that the plugin's pom.xml [references ]( | https://github.com/jenkinsci/covcomplplot-plugin/blob/master/pom.xml#L40 ) ] an old svn repo for Powermock. This has since moved to Github, so it would seem that the repo URL needs to be updated (or removed, if the library is available from the core Jenkins repo). I didn't find any other references to Subversion in the plugin's source code.Can someone confirm this analysis? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe
[JIRA] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Title: Message Title
Mark Waite edited a comment on JENKINS-33984
Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Yes, you would need to specify multiple refspecs behind the advanced button of the repository definition for the job. I assume your {noformat}origin/release**{noformat} branch specifier really means {noformat}origin/release/**{noformat}. I think your refspec should look like this:{noformat}+refs/heads/develop:refs/remotes/origin/develop+refs/heads/release/*:refs/remotes/origin/release/*{noformat}The [git refspecs documentation|https://git-scm.com/book/en/v2/Git-Internals-The-Refspec] gives a very good review of the strengths and weaknesses of refspec definition.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13035) Duplicate Views Tab Bar option
Title: Message Title Ignacio Albors closed an issue as Fixed Jenkins / JENKINS-13035 Duplicate Views Tab Bar option Change By: Ignacio Albors Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title ikedam commented on JENKINS-35081 Re: Separate authorization configuration page I found I mixed up several different problems and tried to resolve them at all. (I made those problems clear in JENKINS-38217) I now believe those problems can be resolved one-by-one. And it also told me that I no longer need to splitting configuration files: It relates not to the original purpose of separating the configuration page but rather to JENKINS-38219 (Restrict Job.CONFIGURE permissions by plugins). It doesn't work as expected until I resolve JENKINS-38219. And once after I resolve JENKINS-38219, I no longer need to split configuration files for security purposes. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26340) Implement SimpleBuildStep for Pipeline Compatibility
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26340 Re: Implement SimpleBuildStep for Pipeline Compatibility Code changed in jenkins User: James Nord Path: pom.xml src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/BackgroundResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/BeforeAfterResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONParser.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultAction.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultArchiver.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/DefaultTestResultParserImpl.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/FeatureResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/ScenarioResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/StepResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/TagResult.java src/test/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONParserTest.java src/test/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONSupportPluginIT.java src/test/resources/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONSupportPluginIT/featureFail.json src/test/resources/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONSupportPluginIT/featurePass.json src/test/resources/org/jenkinsci/plugins/cucumber/jsontestsupport/ScenarioResultTest/cucumber-jvm_examples_java-calculator__cucumber-report.json http://jenkins-ci.org/commit/cucumber-testresult-plugin/d87afb14e45b754d023ca76f2d47e5e3e531780e Log: Merge pull request #8 from helloeve/master JENKINS-26340 Pipeline Integration Compare: https://github.com/jenkinsci/cucumber-testresult-plugin/compare/48dda7f1f2a7...d87afb14e45b Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-26430) non-administrators unable to manually provision new slaves
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26430 Re: non-administrators unable to manually provision new slaves Code changed in jenkins User: James Nord Path: pom.xml src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultAction.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultArchiver.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/TagResult.java src/test/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONParserTest.java src/test/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONSupportPluginIT.java src/test/resources/org/jenkinsci/plugins/cucumber/jsontestsupport/ScenarioResultTest/cucumber-jvm_examples_java-calculator__cucumber-report.json http://jenkins-ci.org/commit/cucumber-testresult-plugin/cd792abaa1bb24ddf39021caff1a38c5bf668ca5 Log: JENKINS-26430 WIP pipeline compatability Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30077) Expand build parameters
Title: Message Title Brantone commented on JENKINS-30077 Re: Expand build parameters Initial attempt at https://github.com/jenkinsci/ws-cleanup-plugin/pull/31 Thoughts? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Thorsten Scherler commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly The PR fixes the steps in parallel nodes. It is a step in the right direction, however I am still seeing the problem of the "flatten" especially in my "input" steps. IMO it is a bug, since before we know that a parallel node is coming however the response now do not wait for both children are present. I never saw this problem while I was developing karaoke but now can reproduce it every time. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38237) Invalid AVD Path / AVD not created
Title: Message Title Adam Kobus updated an issue Jenkins / JENKINS-38237 Invalid AVD Path / AVD not created Change By: Adam Kobus Summary: Invalid AVD Path in build logs / AVD not created Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38235) Ownership plugin assignment strategy does not represent state correctly
Title: Message Title Oleg Nenashev commented on JENKINS-38235 Re: Ownership plugin assignment strategy does not represent state correctly It was an implementation bug introduced in https://github.com/jenkinsci/ownership-plugin/commit/0c8bc4496325edb16214cf3c3b1d7bb1e9144ec0. No impact on the released versions. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7192) Use multiple SCM sources
Title: Message Title Oleg Nenashev reopened an issue "We" in the message below meant "jglick", no more. We have no such roadmap decisions. If somebody wants to implement the feature, such contribution will be really appreciated. It could be done via SCM API extension and integration, but it's definitely not a trivial task Jenkins / JENKINS-7192 Use multiple SCM sources Change By: Oleg Nenashev Resolution: Won't Do Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-19752) Download build artifacts as zip generates a corrupted file
Title: Message Title Luca Moscato commented on JENKINS-19752 Re: Download build artifacts as zip generates a corrupted file Hi all, sadly I'm facing the same issue, here is my environment jenkins 2.7.4 jdk 1.8.40 (too old?) centos 6.8 (package updated every night). It happens that artifacts download (both .zip and other formats) fails often when, in office, the network appears slow. For fail I intend that from browser the download process seems ends correctly ok, but the file downloaded has smaller size and, in case of .zip, can't be opened. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38134) Generate checksums for war, Windows and OS X distributables
Title: Message Title Armando Fernandez started work on JENKINS-38134 Change By: Armando Fernandez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38226) Collapsible View to show only favourites
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38226 Collapsible View to show only favourites Change By: Michael Neale Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38109) Parallel variable expansion
Title: Message Title Daniel Stone commented on JENKINS-38109 Re: Parallel variable expansion Sorry, you're totally right; I'd realised very shortly after posting this that it had nothing to do with parallel itself but block capture/evaluation at best. 'def' of the variable to reduce scope hadn't occurred to me, but makes total sense. Apologies for the noise. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38109) Parallel variable expansion
Title: Message Title Daniel Stone closed an issue as Not A Defect Jenkins / JENKINS-38109 Parallel variable expansion Change By: Daniel Stone Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38235) Ownership plugin assignment strategy does not represent state correctly
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38235 Ownership plugin assignment strategy does not represent state correctly Change By: Oleg Nenashev Summary: Ownership plugin assignment strategy does not represent state correctly after config reload in 2.x Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38235) Ownership plugin assignment strategy does not represent state correctly
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38235 Ownership plugin assignment strategy does not represent state correctly Change By: Oleg Nenashev Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30662) [Dynamic Search View] requests cache implementation is not thread-safe
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-30662 [Dynamic Search View] requests cache implementation is not thread-safe Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36508) Search Bar is Creating Users
Title: Message Title Oleg Nenashev commented on JENKINS-36508 Re: Search Bar is Creating Users Need to check it. Maybe it happens due to filter settings Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32580) Plugin enable/disable information and dependencies are broken
Title: Message Title Arend v. Reinersdorff commented on JENKINS-32580 Re: Plugin enable/disable information and dependencies are broken Daniel Beck I'm sorry, I wasn't aware of that. Thanks for pointing it out Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27552) If deleting older verions, provide option for sorting
Title: Message Title Brantone commented on JENKINS-27552 Re: If deleting older verions, provide option for sorting Will be doing a new release soon, hoping to get a couple more updates in. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38237) Invalid AVD Path / AVD not created
Title: Message Title
Adam Kobus updated an issue
Jenkins / JENKINS-38237
Invalid AVD Path / AVD not created
Change By:
Adam Kobus
{noformat}11:46:06 $ /home/jenkins/android/tools/android list target11:46:07 [android] Using Android SDK: /home/jenkins/android11:46:07 [android] Creating Android AVD: /tmp/.android/avd/hudson_pl-PL_320_768x1280_Google_Inc._Google_APIs_17_armeabi-v7a_-jars-test.avd11:46:07 [android] /home/jenkins/android/tools/android create avd -f -a -c 64M -s 768x1280 -n hudson_pl-PL_320_768x1280_Google_Inc._Google_APIs_17_armeabi-v7a_-jars-test -t "Google Inc.:Google APIs:17" --abi armeabi-v7a11:46:08 [android] Could not create Android emulator: Failed to parse AVD config file{noformat}I checked source code of plugin, and the only place where '/tmp' directory is being set is athttps://github.com/jenkinsci/android-emulator-plugin/blob/master/src/main/java/hudson/plugins/android_emulator/util/Utils.java#L284I investigated this further by creating simple jar, which was then ran in 'execute shell' build step..{code:java}public class Main {public static void main(String[] args) {System.out.println("home: " + System.getenv("HOME"));System.out.println("username: " + System.getProperty("user.name"));}}{code}and here is the output:{noformat}12:39:13 home: null12:39:13 username: jenkins{noformat}When I execute this jar directly from shell over shh ssh it works properly.I have no clue why is it working that way, but have you considered using EnvVars class? It stores all environment variables available on machine, including those injected by plugins / slaves. http://javadoc.jenkins-ci.org/hudson/EnvVars.html
Add Comment
[JIRA] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Michael Neale commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly Vivek Pandey does bismuth help with this at all or will just show the same incorrect state? Thorsten Scherler yes the flattening thing does happen, but I can only make it happen with constrived "sleep" (perhaps we can punt that to another ticket over the more urgent ones, unless you can see it happening with less contrived cases). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38062) "Create Delivery Pipeline version" errors
Title: Message Title Christopher Shannon commented on JENKINS-38062 Re: "Create Delivery Pipeline version" errors FYI - yes you can work around the error message for PIPELINE_VERSION, but what is strange is that we see parameter errors for every parameter that we're sending downstream as well. You have to do the blanket override to get work around this right now. -Dhudson.model.ParametersAction.keepUndefinedParameters=true Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38062) "Create Delivery Pipeline version" errors
Title: Message Title
Henrik Meinardus edited a comment on JENKINS-38062
Re: "Create Delivery Pipeline version" errors
I digged dug a bit further in the commit history. This incompatibility was introduced by resolving SECURITY-170 (commit 57a82505f4dc5de97c57ad1f340561ad9f0159c5 and its follow-up) and can be worked around - as suggested in the warning - by starting the Jenkins Java process with the following additional parameter:{code}-Dhudson.model.ParametersAction.safeParameters=PIPELINE_VERSION{code}Maybe this should be documented on the plugin wiki page until it is fixed?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38234) Make use of filesystem snapshots
Title: Message Title Heiko Nardmann updated an issue Jenkins / JENKINS-38234 Make use of filesystem snapshots Change By: Heiko Nardmann Since many operating systems provide filesystems with a *snapshot* capability I wonder whether it is possible to use this filesystem feature to ease the process of backup up the Jenkins data.The table at [https://en.wikipedia.org/wiki/Comparison_of_file_systems#Features] gives a hint whether a filesystem supports snapshots.No blocking or waiting for Jenkins being idle might be necessary anymore?Problem might be to detect whether the underlying filesystem supports snapshotting and how to use it (without handling each filesystem separately). [This link|https://en.wikipedia.org/wiki/Versioning_file_system] might also be helpful. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an
[JIRA] (JENKINS-38237) Invalid AVD Path in build logs
Title: Message Title
Adam Kobus created an issue
Jenkins / JENKINS-38237
Invalid AVD Path in build logs
Issue Type:
Bug
Assignee:
Christopher Orr
Components:
android-emulator-plugin
Created:
2016/Sep/15 10:47 AM
Environment:
Jenkins 2.1 Android SDK is configured on slave agent, Ubuntu Server LTS 14.04
Priority:
Minor
Reporter:
Adam Kobus
11:46:06 $ /home/jenkins/android/tools/android list target
11:46:07 [android] Using Android SDK: /home/jenkins/android
11:46:07 [android] Creating Android AVD: /tmp/.android/avd/hudson_pl-PL_320_768x1280_Google_Inc._Google_APIs_17_armeabi-v7a_-jars-test.avd
11:46:07 [android] /home/jenkins/android/tools/android create avd -f -a -c 64M -s 768x1280 -n hudson_pl-PL_320_768x1280_Google_Inc._Google_APIs_17_armeabi-v7a_-jars-test -t "Google Inc.:Google APIs:17" --abi armeabi-v7a
11:46:08 [android] Could not create Android emulator: Failed to parse AVD config file
I checked source code of plugin, and the only place where '/tmp' directory is being set is at https://github.com/jenkinsci/android-emulator-plugin/blob/master/src/main/java/hudson/plugins/android_emulator/util/Utils.java#L284 I investigated this further by creating simple jar which executed following code:
public class Main {
public static void main(String[] args) {
[JIRA] (JENKINS-13878) [Max # of builds to keep] can't be configured as global variable
Title: Message Title venkatachalam mani commented on JENKINS-13878 Re: [Max # of builds to keep] can't be configured as global variable Is this issue resolved ? do we have any global variable available for "discard old builds" parameters ? Thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38205) Failed to deploy war on Weblogic: task completed abnormally (exit code = 1)
Title: Message Title Guillermo Figueroa commented on JENKINS-38205 Re: Failed to deploy war on Weblogic: task completed abnormally (exit code = 1) Ok, I get it. I just have the default architecture, with 1 master and without slaves. Regards. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30077) Expand build parameters
Title: Message Title Brantone assigned an issue to Brantone Jenkins / JENKINS-30077 Expand build parameters Change By: Brantone Assignee: vjuranek Brantone Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32452) Badge not visible when job is located in a folder
Title: Message Title Brantone closed an issue as Fixed Jenkins / JENKINS-32452 Badge not visible when job is located in a folder Change By: Brantone Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38233) Enable review builds with pipeline scripts
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-38233 Enable review builds with pipeline scripts Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2016/Sep/15 8:35 AM Priority: Major Reporter: Karl Wirth At the moment it is not possible to trigger a pipelline build using the 'review' URL. This is a problem for Helix Swarm that is not able to trigger pipeline builds and receive the build result. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-32452) Badge not visible when job is located in a folder
Title: Message Title Brantone commented on JENKINS-32452 Re: Badge not visible when job is located in a folder Agreed, and also on 1.651.3 (and quite a few fewer than that if i recall). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38062) "Create Delivery Pipeline version" errors
Title: Message Title Henrik Meinardus commented on JENKINS-38062 Re: "Create Delivery Pipeline version" errors Additional note: The error appears from Jenkins 1.651.2 onward. 1.651.1 runs without problems. Maybe this is somehow connected to JENKINS-34540. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38057) Opening "Global Tool Configuration" or "Global Security" fails
Title: Message Title Luca Faggianelli commented on JENKINS-38057 Re: Opening "Global Tool Configuration" or "Global Security" fails I'm suffering the same issue on Ubuntu 12.04, it happens when I navigate to /credentials. Did you find any work around? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36543) Boolean input parameter ignores default value of false
Title: Message Title
Hendrik Brinkmann edited a comment on JENKINS-36543
Re: Boolean input parameter ignores default value of false
I could reproduce the problem also under the latest weekly release Jenkins ver. 2.22. This issues only occures if you use the {{input}} inside of a {{stage}}-Block and access the checkbox via ui UI (see screenshot) . If you access the checkbox via console the problem does not occure.{code:java}stage ('test') {input message: 'test', parameters: [booleanParam(defaultValue: false, description: '', name: 'A')]}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36543) Boolean input parameter ignores default value of false
Title: Message Title
Hendrik Brinkmann reopened an issue
I could reproduce the problem also under the latest weekly release Jenkins ver. 2.22. This issues only occures if you use the input inside of a stage-Block and access the checkbox via ui. If you access the checkbox via console the problem does not occure.
stage ('test') {
input message: 'test', parameters: [booleanParam(defaultValue: false, description: '', name: 'A')]
}
Jenkins / JENKINS-36543
Boolean input parameter ignores default value of false
Change By:
Hendrik Brinkmann
Resolution:
Cannot Reproduce
Status:
Resolved Reopened
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-19752) Download build artifacts as zip generates a corrupted file
Title: Message Title Luca Moscato updated an issue Jenkins / JENKINS-19752 Download build artifacts as zip generates a corrupted file Change By: Luca Moscato The zip generated by the link http://server/job/myJob/lastSuccessfulBuild/artifact/*zip*/archive.zip generates a zip file in which everything seems ok, but when you try to unzip the content with 7z for instance, it fails (compression method not supported). I can't see anything in the logs. BTW, the size of the file in the archive are set to 0. Could be a side effect in 7z.It works fine with 1.531.And finally, there was a modification of something about the compression in 1.532 related to issue JENKINS-19473. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-26700) Download build artifacts as zip generates a corrupted file
Title: Message Title Luca Moscato commented on JENKINS-26700 Re: Download build artifacts as zip generates a corrupted file Hi all, sadly I'm facing the same issue, here is my environment jenkins 2.7.4 jdk 1.8.40 (too old?) centos 6.8 (package updated every night). It happens that artifacts download (both .zip and other formats) fails often when, in office, the network appears slow. For fail I intend that from browser the download process seems ends correctly ok, but the file downloaded has smaller size and, in case of .zip, can't be opened. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28881) Add support for CloudBees folder plugin
Title: Message Title Oleg Nenashev commented on JENKINS-28881 Re: Add support for CloudBees folder plugin I have to demo it at Jenkins world I'm working on "0.9-rc-1", to be released today. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38239) "Discard Old Builds" parameters as a environmental variable
Title: Message Title venkatachalam mani created an issue Jenkins / JENKINS-38239 "Discard Old Builds" parameters as a environmental variable Issue Type: Improvement Assignee: nkns165 Components: discard-old-build-plugin Created: 2016/Sep/15 11:32 AM Priority: Minor Reporter: venkatachalam mani 7 10 -1 -1 Is there any way, we can create discard old builds parameters as a environment variable. So that those variables can be applied to all jobs instead of maintaining at the job level. Add Comment
[JIRA] (JENKINS-38235) Ownership plugin assignment strategy does not represent state correctly
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-38235 Ownership plugin assignment strategy does not represent state correctly Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38236) NPE when Ownership plugin receives a null Copy policy from broken form submission
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38236 Re: NPE when Ownership plugin receives a null Copy policy from broken form submission Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/OwnershipDescriptionHelper.java http://jenkins-ci.org/commit/ownership-plugin/1c9e0930db41dbc706ebc10ad1e7c2c3bf0007bd Log: [FIXED JENKINS-38238] - Properly handle user lists for build wrappers (#51) The change prevents the proken item separation in the list. https://issues.jenkins-ci.org/browse/JENKINS-38236 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38235) Ownership plugin assignment strategy does not represent state correctly
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38235 Re: Ownership plugin assignment strategy does not represent state correctly Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/OwnershipPluginConfiguration.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/extensions/ItemOwnershipPolicy.java http://jenkins-ci.org/commit/ownership-plugin/2550b2393616033df0f0f09dc50993c421625b85 Log: Merge pull request #52 from oleg-nenashev/bug/JENKINS-38236-real [JENKINS38236,JENKINS-38235] - Prevent issues during ItemPolicy handling Compare: https://github.com/jenkinsci/ownership-plugin/compare/1c9e0930db41...2550b2393616 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38236) NPE when Ownership plugin receives a null Copy policy from broken form submission
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38236 Re: NPE when Ownership plugin receives a null Copy policy from broken form submission Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/OwnershipPluginConfiguration.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/extensions/ItemOwnershipPolicy.java http://jenkins-ci.org/commit/ownership-plugin/2550b2393616033df0f0f09dc50993c421625b85 Log: Merge pull request #52 from oleg-nenashev/bug/JENKINS-38236-real [JENKINS38236,JENKINS-38235] - Prevent issues during ItemPolicy handling Compare: https://github.com/jenkinsci/ownership-plugin/compare/1c9e0930db41...2550b2393616 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38238) NODE/JOB_COOWNERS comma-separated list of items is broken in Freestyle build wrappers
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38238 Re: NODE/JOB_COOWNERS comma-separated list of items is broken in Freestyle build wrappers Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/OwnershipDescriptionHelper.java http://jenkins-ci.org/commit/ownership-plugin/1c9e0930db41dbc706ebc10ad1e7c2c3bf0007bd Log: [FIXED JENKINS-38238] - Properly handle user lists for build wrappers (#51) The change prevents the proken item separation in the list. https://issues.jenkins-ci.org/browse/JENKINS-38236 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38235) Ownership plugin assignment strategy does not represent state correctly
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38235 Re: Ownership plugin assignment strategy does not represent state correctly Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/extensions/ItemOwnershipPolicy.java http://jenkins-ci.org/commit/ownership-plugin/e9e188361a3859bb7defa4cd4cf932f66aede59d Log: [FIXED JENKINS-38235] - eturn proper descriptor for ItemOwnershipPolicy implementations Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28881) Add support for CloudBees folder plugin
Title: Message Title Brantone commented on JENKINS-28881 Re: Add support for CloudBees folder plugin Chance of release? Maybe after Jenkins World? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19664) Archived artifact of promoted build corrupted after download!
Title: Message Title Luca Moscato commented on JENKINS-19664 Re: Archived artifact of promoted build corrupted after download! Hi all, sadly I'm facing the same issue, here is my environment jenkins 2.7.4 jdk 1.8.40 (too old?) centos 6.8 (package updated every night). It happens that artifacts download (both .zip and other formats) fails often when, in office, the network appears slow. For fail I intend that from browser the download process seems ends correctly ok, but the file downloaded has smaller size and, in case of .zip, can't be opened. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38226) Collapsible View to show only favourites
Title: Message Title Michael Neale commented on JENKINS-38226 Re: Collapsible View to show only favourites James Dumay worth looking at I think? I wonder if this could re-purpose personalisation as a build monitor. Currently personalisation requires a logged in user, however, which is not optimal for multi user build monitors, but this is a step in an interesting direction. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38062) "Create Delivery Pipeline version" errors
Title: Message Title Henrik Meinardus commented on JENKINS-38062 Re: "Create Delivery Pipeline version" errors I digged a bit further in the commit history. This incompatibility was introduced by resolving SECURITY-170 (commit 57a82505f4dc5de97c57ad1f340561ad9f0159c5 and its follow-up) and can be worked around - as suggested in the warning - by starting the Jenkins Java process with the following additional parameter: -Dhudson.model.ParametersAction.safeParameters=PIPELINE_VERSION Maybe this should be documented on the plugin wiki page until it is fixed? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38237) Invalid AVD Path / AVD not created
Title: Message Title
Adam Kobus updated an issue
Jenkins / JENKINS-38237
Invalid AVD Path / AVD not created
Change By:
Adam Kobus
{noformat}11:46:06 $ /home/jenkins/android/tools/android list target11:46:07 [android] Using Android SDK: /home/jenkins/android11:46:07 [android] Creating Android AVD: /tmp/.android/avd/hudson_pl-PL_320_768x1280_Google_Inc._Google_APIs_17_armeabi-v7a_-jars-test.avd11:46:07 [android] /home/jenkins/android/tools/android create avd -f -a -c 64M -s 768x1280 -n hudson_pl-PL_320_768x1280_Google_Inc._Google_APIs_17_armeabi-v7a_-jars-test -t "Google Inc.:Google APIs:17" --abi armeabi-v7a11:46:08 [android] Could not create Android emulator: Failed to parse AVD config file{noformat}I checked source code of plugin, and the only place where '/tmp' directory is being set is athttps://github.com/jenkinsci/android-emulator-plugin/blob/master/src/main/java/hudson/plugins/android_emulator/util/Utils.java#L284I investigated this further by creating simple jar , which executed following code: was then ran in 'execute shell' build step.. {code:java}public class Main {public static void main(String[] args) {System.out.println("home: " + System.getenv("HOME"));System.out.println("username: " + System.getProperty("user.name"));}}{code}and here is the output:{noformat}12:39:13 home: null12:39:13 username: jenkins{noformat} When I execute this jar directly from shell over shh it works properly.I have no clue why is it working that way, but have you considered using EnvVars class? It stores all environment variables available on machine, including those injected by plugins / slaves. http://javadoc.jenkins-ci.org/hudson/EnvVars.html
Add Comment
