[JIRA] (JENKINS-44849) Changeset for first run of generated job is empty
Title: Message Title Stepan Mazurov commented on JENKINS-44849 Re: Changeset for first run of generated job is empty Wayne Warren absolutely agreed - changeset is useless in any type of advanced use case. Thank you for the workaround! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-40866) docker.inside() like syntax that keeps the workspace
Title: Message Title
Stepan Mazurov edited a comment on JENKINS-40866
Re: docker.inside() like syntax that keeps the workspace
Hey, [~abayer], thank you for adding this, I noticed that its not in ` {{ syntax.md ` }} or the wiki (under changelog), might want to add that so other people can find 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-40866) docker.inside() like syntax that keeps the workspace
Title: Message Title Stepan Mazurov commented on JENKINS-40866 Re: docker.inside() like syntax that keeps the workspace Hey, Andrew Bayer, thank you for adding this, I noticed that its not in `syntax.md` or the wiki (under changelog), might want to add that so other people can find 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-41012) when {branch} stage conditional is busted (mostly)
Title: Message Title
Stepan Mazurov commented on JENKINS-41012
Re: when {branch} stage conditional is busted (mostly)
Glad I could help! Thank you for those words, I appreciate 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-41012) when {branch} stage conditional is busted (mostly)
Title: Message Title
Stepan Mazurov commented on JENKINS-41012
Re: when {branch} stage conditional is busted (mostly)
No worries, this is beta software after all, thanks for taking care of 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-41012) when {} branch conditional is busted (mostly)
Title: Message Title
Stepan Mazurov created an issue
Jenkins / JENKINS-41012
when {} branch conditional is busted (mostly)
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Jan/12 12:42 AM
Environment:
Jenkins: 2.40 (docker) Pipeline: Model Definition: 0.8.1 SCM API Plugin: 2.0.1-beta-2 pipeline: Multibranch: 2.10-beta-1
Priority:
Minor
Reporter:
Stepan Mazurov
Just installed latest pipeline-model-definition plugin (0.8.1) and was trying to set up a when branch stage condition. In short, only way to make branch matching work is via _expression_, evaluating env.BRANCH_NAME directly:
when {
_expression_ {
return env.BRANCH_NAME == "feature/docker"
}
}
This is in a branch feature/docker job of a multi-branch pipeline I tried other permutation of the conditional, and it did not work, the stage would get skipped (steps were not executed):
when {
branch "feature/docker"
}
when {
environment name: "BRANCH_NAME", value: "feature/dock
[JIRA] (JENKINS-41012) when {branch} stage conditional is busted (mostly)
Title: Message Title
Stepan Mazurov updated an issue
Jenkins / JENKINS-41012
when {branch} stage conditional is busted (mostly)
Change By:
Stepan Mazurov
Summary:
when { } branch } stage conditional is busted (mostly)
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] [git-plugin] (JENKINS-12545) Jenkins should build all tracked branches that have changed when triggered by Github
Title: Message Title Stepan Mazurov commented on JENKINS-12545 Re: Jenkins should build all tracked branches that have changed when triggered by Github Mark Waite I effectively did same repro steps as you, with 2 changes: 1. I did not have any post-receive hooks set up, simply SCM poll every minute 2. The "origin" repo was on github Does it work correctly for you if you remove post-receive hook and simply poll? Kanstantsin Shautsou is there anything else I could do to help fix this? Its quite a big issue that I would love to resolve. Effectively all git-flow type workflows are affected. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-oauth-plugin] (JENKINS-17539) Swarm clients fail to connect if GitHub for authentication
Title: Message Title
Stepan Mazurov edited a comment on JENKINS-17539
Re: Swarm clients fail to connect if GitHub for authentication
{quote}Stepan Mazurov how are you connecting with the swarm plugin? Are you using the GitHub personal access token?{quote}Yes.{quote}Another thing you could try is just setting se-jenkins as an admin.{quote}This indeed did work, but was too permissive for my taste. {quote}Also, contributions are welcome for slave users setting.{quote}I took a look at the code, and to implement it in a way I want (add a field to specify slave users to commiter strategy settings), it appears it would require to modify a lot of code as it would be another discrete strategy permission . I do not feel like the added convince over Matrix strategy is worth the tech debt of adding such functionality. I can now confirm that, with matrix strategy (or commiter strategy with bot account having admin access), a dedicated github "bot" account with a _personal access token_ allows slaves to correctly connect, register themselves and execute tasks. I believe this issue can be considered resolved.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [github-oauth-plugin] (JENKINS-17539) Swarm clients fail to connect if GitHub for authentication
Title: Message Title Stepan Mazurov commented on JENKINS-17539 Re: Swarm clients fail to connect if GitHub for authentication Stepan Mazurov how are you connecting with the swarm plugin? Are you using the GitHub personal access token? Yes. Another thing you could try is just setting se-jenkins as an admin. This indeed did work, but was too permissive for my taste. Also, contributions are welcome for slave users setting. I took a look at the code, and to implement it in a way I want (add a field to specify slave users to commiter strategy settings), it appears it would require to modify a lot of code as it would be another discrete strategy. I do not feel like the added convince over Matrix strategy is worth the tech debt of adding such functionality. I can now confirm that, with matrix strategy (or commiter strategy with bot account having admin access), a dedicated github "bot" account with a personal access token allows slaves to correctly connect, register themselves and execute tasks. I believe this issue can be considered resolved. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-oauth-plugin] (JENKINS-17539) Swarm clients fail to connect if GitHub for authentication
Title: Message Title Stepan Mazurov commented on JENKINS-17539 Re: Swarm clients fail to connect if GitHub for authentication I am indeed using Github Commiter Authorization Strategy. I switched to matrix and added se-jenkins to slave permissions. Shame I can't use Commiter startegy. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-oauth-plugin] (JENKINS-17539) Swarm clients fail to connect if GitHub for authentication
Title: Message Title Stepan Mazurov commented on JENKINS-17539 Re: Swarm clients fail to connect if GitHub for authentication This is where the permission is checked: https://github.com/jenkinsci/swarm-plugin/blob/f7b9f88a79ae6557135e0cb8360b8d5aa9d5e931/plugin/src/main/java/hudson/plugins/swarm/PluginImpl.java#L54 https://github.com/jenkinsci/swarm-plugin/blob/f7b9f88a79ae6557135e0cb8360b8d5aa9d5e931/plugin/src/main/java/hudson/plugins/swarm/PluginImpl.java#L157 Adding se-jenkins as an admin works around the issue, but its not fantastic. Given that the security for that user is lax (its used as a bot and a shared ssh key), giving it admin permissions to jenkins is pretty bad. Ideally, the fix would be to add another field to specify "SlaveComputer" users. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-oauth-plugin] (JENKINS-17539) Swarm clients fail to connect if GitHub for authentication
Title: Message Title Stepan Mazurov commented on JENKINS-17539 Re: Swarm clients fail to connect if GitHub for authentication I get the following error: While serving http://10.7.0.1:8080/plugin/swarm/slaveInfo: hudson.security.AccessDeniedException2: se-jenkins is missing the Slave/Create permission We have a se-jenkins user on github that is part of our organization. I'm unsure on how to give that user slave/create permission Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-12545) Jenkins should build all tracked branches that have changed when triggered by Github
Title: Message Title
Stepan Mazurov edited a comment on JENKINS-12545
Re: Jenkins should build all tracked branches that have changed when triggered by Github
Unfortunately, I do not have ability to run locally with a debugger. I will, however, share as much info as possible.My github hook log when i pushed {{develop}} and {{master}} at the same time:{code}Using strategy: Default[poll] Last Built Revision: Revision [sha1] (origin/develop) > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repositories > git config remote.origin.url git@[github url] # timeout=10Pruning obsolete local branchesFetching upstream changes from [github url] > git --version # timeout=10using GIT_SSH to set credentials A Deploy user > git -c core.askpass=true fetch --tags --progress [github url] +refs/heads/*:refs/remotes/origin/* --prunePolling for changes inSeen branch in repository origin/developSeen branch in repository origin/masterSeen 2 remote branches > git log --full-history --no-abbrev --format=raw -M -m --raw [older sha1]..[sha 1] # timeout=10Done. Took 3.1 secChanges found{code}Only {{develop}} built.I then switched the trigger from *Build when a change is pushed to GitHub* to *Poll SCM*, and it still only built 1 branch.Here are the logs:{code}Using strategy: Default[poll] Last Built Revision: Revision [sha1] (origin/develop) > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repositories > git config remote.origin.url [github project] # timeout=10Pruning obsolete local branchesFetching upstream changes from [github project] > git --version # timeout=10using GIT_SSH to set credentials A Deploy user > git -c core.askpass=true fetch --tags --progress [github project] +refs/heads/*:refs/remotes/origin/* --prunePolling for changes inSeen branch in repository origin/developSeen branch in repository origin/masterSeen 2 remote branchesDone. Took 1.1 secNo changes{code}{{github-plugin}} version: {{1.11.3}} *Edit:* and {{1.12.0}}, functionality unchanged {{git-plugin}} version: {{2.4.0}} {{git-client}} version: {{1.18.0}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because
[JIRA] [git-plugin] (JENKINS-12545) Jenkins should build all tracked branches that have changed when triggered by Github
Title: Message Title Stepan Mazurov commented on JENKINS-12545 Re: Jenkins should build all tracked branches that have changed when triggered by Github Unfortunately, I do not have ability to run locally with a debugger. I will, however, share as much info as possible. My github hook log when i pushed develop and master at the same time: Unable to find source-code formatter for language: bash. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml Using strategy: Default [poll] Last Built Revision: Revision [sha1] (origin/develop) > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repositories > git config remote.origin.url git@[github url] # timeout=10 Pruning obsolete local branches Fetching upstream changes from [github url] > git --version # timeout=10 using GIT_SSH to set credentials A Deploy user > git -c core.askpass=true fetch --tags --progress [github url] +refs/heads/*:refs/remotes/origin/* --prune Polling for changes in Seen branch in repository origin/develop Seen branch in repository origin/master Seen 2 remote branches > git log --full-history --no-abbrev --format=raw -M -m --raw [older sha1]..[sha 1] # timeout=10 Done. Took 3.1 sec Changes found Only develop built. I then switched the trigger from Build when a change is pushed to GitHub to Poll SCM, and it still only built 1 branch. Here are the logs: Using strategy: Default [poll] Last Built Revision: Revision [sha1] (origin/develop) > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repositories > git config remote.origin.url [github project] # timeout=10 Pruning obsolete local branches Fetching upstream changes from [github project] > git --version # timeout=10 using GIT_SSH to set credentials A Deploy user > git -c core.askpass=true fetch --tags --progress [github project] +refs/heads/*:refs/remotes/origin/* --prune Polling for changes in Seen branch in repository origin/develop Seen branch in repository origin/master Seen 2 remote branches Done. Took 1.1 sec No changes github-plugin version: 1.11.3 git-plugin version: 2.4.0 Add Comment
[JIRA] [git-plugin] (JENKINS-12545) Jenkins should build all tracked branches that have changed when triggered by Github
Title: Message Title
Stepan Mazurov edited a comment on JENKINS-12545
Re: Jenkins should build all tracked branches that have changed when triggered by Github
Unfortunately, I do not have ability to run locally with a debugger. I will, however, share as much info as possible.My github hook log when i pushed {{develop}} and {{master}} at the same time:{code :bash }Using strategy: Default[poll] Last Built Revision: Revision [sha1] (origin/develop) > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repositories > git config remote.origin.url git@[github url] # timeout=10Pruning obsolete local branchesFetching upstream changes from [github url] > git --version # timeout=10using GIT_SSH to set credentials A Deploy user > git -c core.askpass=true fetch --tags --progress [github url] +refs/heads/*:refs/remotes/origin/* --prunePolling for changes inSeen branch in repository origin/developSeen branch in repository origin/masterSeen 2 remote branches > git log --full-history --no-abbrev --format=raw -M -m --raw [older sha1]..[sha 1] # timeout=10Done. Took 3.1 secChanges found{code}Only {{develop}} built.I then switched the trigger from *Build when a change is pushed to GitHub* to *Poll SCM*, and it still only built 1 branch.Here are the logs:{code}Using strategy: Default[poll] Last Built Revision: Revision [sha1] (origin/develop) > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repositories > git config remote.origin.url [github project] # timeout=10Pruning obsolete local branchesFetching upstream changes from [github project] > git --version # timeout=10using GIT_SSH to set credentials A Deploy user > git -c core.askpass=true fetch --tags --progress [github project] +refs/heads/*:refs/remotes/origin/* --prunePolling for changes inSeen branch in repository origin/developSeen branch in repository origin/masterSeen 2 remote branchesDone. Took 1.1 secNo changes{code}{{github-plugin}} version: {{1.11.3}}{{git-plugin}} version: {{2.4.0}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscrib
[JIRA] [github-plugin] (JENKINS-12545) Jenkins should build all tracked branches that have changed when triggered by Github
Title: Message Title
Stepan Mazurov commented on JENKINS-12545
Re: Jenkins should build all tracked branches that have changed when triggered by Github
Hi, this appears to continue being an issue, are there any solutions? Im personally not a fan of the {[multi-branch}} plugin
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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.
