[JIRA] (JENKINS-42450) Efficiently add a single repo to a github org without requiring a full scan
Title: Message Title Leandro Lucarella commented on JENKINS-42450 Re: Efficiently add a single repo to a github org without requiring a full scan How was this fixed exactly? I still can't find any way to trigger a discovery on a new project without going through a whole organization scan, which for us is horribly slow and it exhausts all the GitHub API rate limit. Each time a new project is created, we basically have to wait for a day to see it in Jenkins... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179362.1488506928000.2413.1562342940211%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) HTTP ERROR 403
Title: Message Title Leandro Lucarella commented on JENKINS-57154 Re: HTTP ERROR 403 In case it helps anyone dealing with this, I re-upgraded to 0.32 after applying some changes in 0.31. If I need to do more changes I will downgrade and upgrade again. Very far from the ideal, but it works as a workaround and you end up having /only/ a small window where you are vulnerable Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) HTTP ERROR 403
Title: Message Title Leandro Lucarella commented on JENKINS-57154 Re: HTTP ERROR 403 Also affected, same description, first user is retrieved correctly, all the following are errors, and any attempt to save the configuration for the security page ends in a "No valid crumb was included in the request" 403 error. Ddowngrading to version 0.31 fixed it for me too, but then I'm exposed to the CSRF vulnerability Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54495) Better handling of GitHub Organization folder scan to avoid API quota
Title: Message Title Leandro Lucarella created an issue Jenkins / JENKINS-54495 Better handling of GitHub Organization folder scan to avoid API quota Issue Type: Improvement Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-11-06 15:32 Environment: Jenkins ver. 2.138.2 GitHub Branch Source Plugin 2.4.1 Labels: performance user-experience github api quota Priority: Major Reporter: Leandro Lucarella When having a big GitHub organization, with hundreds of repos, each with hundreds of branches and tags, refreshing the whole organization is not possible (or it takes ages) due to GitHub API quota being hit. This is particularly bad when trying to add a new repo, it could take days, which is completely impractical. There are several solutions to this issue that I can think of: Use GitHub GraphQL API to query the whole thing in one (or very few) request(s) Make a "shallow scan", that only discovers repos. Then each repo can be refreshed separately, which can 1. enable the quick addition of new repos and 2. distribute the refresh API bursts in time making hitting the API quota less likely Add a separate function to only discover one repo specified by the user
[JIRA] (JENKINS-42450) Efficiently add a single repo to a github org without requiring a full scan
Title: Message Title Leandro Lucarella commented on JENKINS-42450 Re: Efficiently add a single repo to a github org without requiring a full scan BTW, this is marked as resolved but I can't find what's the solution and how to use it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42450) Efficiently add a single repo to a github org without requiring a full scan
Title: Message Title Leandro Lucarella commented on JENKINS-42450 Re: Efficiently add a single repo to a github org without requiring a full scan Any news on this one? I'm bumping into this problem, specially because scanning the full org will make Jenkins hit the API quota limit. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title Leandro Lucarella commented on JENKINS-47496 Re: No automatic builds for tags you could have a build storm when checking out a repository I don't get this. What do you mean? I'm quite surprised by this design decision, other CI system build tags automatically and I never had any problems with it. Checking out the repository where could have a build storm? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-37781) Pipeline Config: ability to skip whole pipeline or stages based on boolean condition
Title: Message Title
Leandro Lucarella edited a comment on JENKINS-37781
Re: Pipeline Config: ability to skip whole pipeline or stages based on boolean condition
Sorry, I think I got the comments mixed up, I was replying about scripted pipelines: > {quote} => therefore filed https://issues.jenkins-ci.org/browse/JENKINS-47286 "Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view" {quote}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-37781) Pipeline Config: ability to skip whole pipeline or stages based on boolean condition
Title: Message Title Leandro Lucarella commented on JENKINS-37781 Re: Pipeline Config: ability to skip whole pipeline or stages based on boolean condition Sorry, I think I got the comments mixed up, I was replying about scripted pipelines: > => therefore filed https://issues.jenkins-ci.org/browse/JENKINS-47286 "Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
Title: Message Title Leandro Lucarella commented on JENKINS-47286 Re: Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view +1 Even when the issue proper here concerns me, I find it very worrying that there are features that are planned to be only available in declarative when I thought declarative was just a convenient simplification of scripted pipelines for people only needing very simple pipelines. Is obvious that when it comes to complex pipelines, or even sharing code (reuse possibilities are very crippled in declarative, as one can't put stages or stuff like agent or triggers in a library), there is no other option but scripted pipelines. It seems crazy (and backwards) to make scripted pipelines a second-class citizen. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-37781) Pipeline Config: ability to skip whole pipeline or stages based on boolean condition
Title: Message Title Leandro Lucarella commented on JENKINS-37781 Re: Pipeline Config: ability to skip whole pipeline or stages based on boolean condition It's "resolved" as POSTPONED. So it's not fixed. Also, closing issues like that doesn't allow people to vote for them, which kind of sucks (I've seen it for other issues like supporting labels to steps). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42624) Custom title for build steps
Title: Message Title Leandro Lucarella commented on JENKINS-42624 Re: Custom title for build steps That's not enough. Plug-in writers won't be able to know users needs. For example, I have a case where I use the `checkout` step to get code from more than one repo, I would like to be able to describe what each checkout is about. How could the plug-in writer know how this is best represented. Should they use the URL? The branch? Maybe some directory if the sparse checkout plug-in is used? It makes no sense to put this on the side of the plug-in writer. The user knows best. Also effort wise, for me is trivial to add some `@Step(title='Checkout main component')` while implementing all sort of heuristics to try to guess what the user wants for a plug-in writer would be madness. Please reopen. This Issue makes a lot of sense. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42286) [REGRESSION] Dockerfile filename cannot contain directory separators
Title: Message Title Leandro Lucarella commented on JENKINS-42286 Re: [REGRESSION] Dockerfile filename cannot contain directory separators Thanks for the quick response! 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-42286) [REGRESSION] Dockerfile filename cannot contain directory separators
Title: Message Title Leandro Lucarella created an issue Jenkins / JENKINS-42286 [REGRESSION] Dockerfile filename cannot contain directory separators Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2017/Feb/23 3:24 PM Environment: version 1.0.2 Labels: regression pipeline Priority: Blocker Reporter: Leandro Lucarella With the last upgrade to 1.0.2 I'm getting this error: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 4: Dockerfile filename cannot contain directory separators. @ line 4, column 13. filename 'docker/Dockerfile' ^ Docker accepts directory separators! And this worked before.
[JIRA] (JENKINS-41668) No way to specify directory for dockerfile
Title: Message Title Leandro Lucarella commented on JENKINS-41668 Re: No way to specify directory for dockerfile Thanks a lot for the quick response. I found a workaround though, I can use a `.dockerignore` file with: * !docker/ That would make the image building process to ignore everything outside the docker directory, which is what I wanted. Nevertheless, I think is a good feature to have in pipeline models, specially a `build_args` option since it makes it as flexible and future-proof as it can get. 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-41668) No way to specify directory for dockerfile
Title: Message Title Leandro Lucarella commented on JENKINS-41668 Re: No way to specify directory for dockerfile For example, for a very simple project with a Dockerfile in docker/: docker build -t test -f docker/Dockerfile . -> Sending build context to Docker daemon 9.861 MB docker build -t test -f docker/Dockerfile docker -> Sending build context to Docker daemon 2.048 kB Sending ~10MB vs sending 2KB. I really hope this issue gets addressed soon because it blocking us from using declarative pipelines as all our projects use this trick to avoid so much copying to the docker daemon... 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-41668) No way to specify directory for dockerfile
Title: Message Title Leandro Lucarella created an issue Jenkins / JENKINS-41668 No way to specify directory for dockerfile Issue Type: Improvement Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2017/Feb/02 5:02 PM Priority: Minor Reporter: Leandro Lucarella It looks like there is no way to specify a directory to build an image using the "dockerfile" option. It only supports "filename", which is analogous to "-f" for the "docker build" command-line, but "docker build" takes as a required argument the DIRECTORY. This is necessary if you don't want the docker daemon to copy the whole repository when making the image, and you want instead to export just a small subset of files. Maybe adding something like "build_args" could be more flexible. Add Comment
[JIRA] (JENKINS-40446) Links broken in GitHub status for matrix projects
Title: Message Title Leandro Lucarella commented on JENKINS-40446 Re: Links broken in GitHub status for matrix projects I can confirm now matrix job links works well with both slack and e-mail notifications. 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-40446) Links broken in GitHub status for matrix projects
Title: Message Title Leandro Lucarella commented on JENKINS-40446 Re: Links broken in GitHub status for matrix projects Cool! 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-40446) Links broken in GitHub status for matrix projects
Title: Message Title Leandro Lucarella commented on JENKINS-40446 Re: Links broken in GitHub status for matrix projects io.jenkins.blueocean:blueocean:1.0.0-b19 org.jenkins-ci.plugins:blueocean-display-url:1.3 org.jenkins-ci.plugins:display-url-api:0.5 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-40446) Links broken in GitHub status for matrix projects
Title: Message Title Leandro Lucarella commented on JENKINS-40446 Re: Links broken in GitHub status for matrix projects Sorry, is not the GitHub status that has a wrong link, is e-mail and slack notifications. Should I create another issue? 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-40446) Links broken in GitHub status for matrix projects
Title: Message Title Leandro Lucarella commented on JENKINS-40446 Re: Links broken in GitHub status for matrix projects BTW, I'm trying this again on beta 18 and sadly it is still broken. Links put in GitHub statuses are still broken. Same if you want to access a project URL directly (https://jenkins/blue/organizations/jenkins/thefolder%2Ftheproject) following the original example. It just shows a regular blueocean project but with no branches or PRs, all empty, and no redirection is performed. As it is, blueocean links are still unusable with matrix jobs and makes github statuses links unusable. 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-40446) Links broken in GitHub status for matrix projects
Title: Message Title Leandro Lucarella reopened an issue Ah, sorry, please see the previous comment. Jenkins / JENKINS-40446 Links broken in GitHub status for matrix projects Change By: Leandro Lucarella Resolution: Fixed 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 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-40446) Links broken in GitHub status for matrix projects
Title: Message Title Leandro Lucarella commented on JENKINS-40446 Re: Links broken in GitHub status for matrix projects FYI, I can't disable the "BlueOcean Display URL" plugin without also disabling the "BlueOcean beta" plugin 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-40446) Links broken in GitHub status for matrix projects
Title: Message Title Leandro Lucarella commented on JENKINS-40446 Re: Links broken in GitHub status for matrix projects Thanks for the quick response! 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-40446) Links broken in GitHub status for matrix projects
Title: Message Title Leandro Lucarella created an issue Jenkins / JENKINS-40446 Links broken in GitHub status for matrix projects Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2016/Dec/14 2:53 PM Environment: Jenkins 2.19.4, Blue Ocean 1.0.0-b13 Priority: Major Reporter: Leandro Lucarella When using blue ocean (I think starting from beta 11 or so), the links in GitHub status were replaced by BlueOcean links, but, at least for matrix projects, these links are broken, for example this is a matrix project that lives in a folder "thefolder" and is called "theproject" in Jenkins, the link used by blueocean is: https://jenkins/blue/organizations/jenkins/thefolder%2Ftheproject%2FDIST%3Dtrusty/detail/trusty/921/pipeline while the correct non-blue ocean link is: https://jenkins/job/thefolder/job/theproject/921/DIST=trusty/ Going through the blue ocean web interface to the project, nothing is even shown. If this can't be fixed soon, there should be at least an option to enable/disable replacing conventional links with blue ocean links, this makes using blue ocean practically impossible with github testing.
[JIRA] (JENKINS-37495) [REGRESSION] Git Submodules having a name different to their path in working tree, failing to checkout
Title: Message Title Leandro Lucarella commented on JENKINS-37495 Re: [REGRESSION] Git Submodules having a name different to their path in working tree, failing to checkout Thanks Ethan, this is a nasty regression that prevent a lot of users from upgrading. It would be nice if it can get some attention! 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-39507) Add a way to use a docker agent that creates the image like with the `docker.create()` function.
Title: Message Title Leandro Lucarella created an issue Jenkins / JENKINS-39507 Add a way to use a docker agent that creates the image like with the `docker.create()` function. Issue Type: Improvement Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2016/Nov/04 1:27 PM Priority: Blocker Reporter: Leandro Lucarella Currently there is no way to create a docker container from an image that is specified by a Dockerfile in the repository. I guess there should be a syntax like: agent docker:create dockerFile:'Dockerfile' dockerDir:'.' Where dockerFile and dockerDir are optional and it defaults to just use the Dockerfile and usual. Add Comment
[JIRA] (JENKINS-37495) Git Submodules having a name different to their path in working tree, failing to checkout
Title: Message Title Leandro Lucarella updated an issue Jenkins / JENKINS-37495 Git Submodules having a name different to their path in working tree, failing to checkout Change By: Leandro Lucarella Priority: Major Critical 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-37495) [REGRESSION] Git Submodules having a name different to their path in working tree, failing to checkout
Title: Message Title Leandro Lucarella updated an issue Jenkins / JENKINS-37495 [REGRESSION] Git Submodules having a name different to their path in working tree, failing to checkout Change By: Leandro Lucarella Summary: [REGRESSION] Git Submodules having a name different to their path in working tree, failing to checkout 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-38409) Cancel ongoing testing of current PR if the PR gets updated with new/changed commits
Title: Message Title Leandro Lucarella commented on JENKINS-38409 Re: Cancel ongoing testing of current PR if the PR gets updated with new/changed commits BTW, for this plugin is even worse, because there seems to be no way to tell jenkins to not run multiple jobs in parallel for one branch/PR, so rapidly updating a PR will just trigger loads of jobs running in parallel, creating some sort of internal DoS for other jobs, which is particularly bad for workflows when doing small, frequent updates to PRs is common. 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-38409) Cancel ongoing testing of current PR if the PR gets updated with new/changed commits
Title: Message Title Leandro Lucarella created an issue Jenkins / JENKINS-38409 Cancel ongoing testing of current PR if the PR gets updated with new/changed commits Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: github-organization-folder-plugin Created: 2016/Sep/21 11:13 AM Environment: Jenkins 2.7.4 Priority: Major Reporter: Leandro Lucarella This was introduced recently in the GitHub integration plugin. Is kind of pointless to keep testing an outdated PR once the code in it was changed, so there should be an option to, in the case of a PR code update (changed or new commits), current and queued job(s) for that PR should be aborted and only the job testing the last changes should run. Add Comment
[JIRA] (JENKINS-37495) Git Submodules having a name different to their path in working tree, failing to checkout
Title: Message Title Leandro Lucarella commented on JENKINS-37495 Re: Git Submodules having a name different to their path in working tree, failing to checkout Oh, yeah, this is nasty, I had to downgrade. 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] [core] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Leandro Lucarella commented on JENKINS-34775 Re: Broken jobs after upgrade to 1.651.2 security update Yes, I am, so it could be that. 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] [core] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title
Leandro Lucarella edited a comment on JENKINS-34775
Re: Broken jobs after upgrade to 1.651.2 security update
After recording artefact’s fingerprints:{noformat}Recording test resultsArchiving artifactsRecording fingerprintsFATAL: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationTokenjava.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken at org.jenkinsci.plugins.GithubSecurityRealm.loadUserByUsername(GithubSecurityRealm.java:644) at hudson.model.User$UserIDCanonicalIdResolver.resolveCanonicalId(User.java:1049)...{noformat}The step after recording fingerprints in the job there is the Chuck Norris plugin and that's the last step in the job.
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] [core] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Leandro Lucarella commented on JENKINS-34775 Re: Broken jobs after upgrade to 1.651.2 security update After recording fingerprints: Recording test results Archiving artifacts Recording fingerprints FATAL: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken java.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken at org.jenkinsci.plugins.GithubSecurityRealm.loadUserByUsername(GithubSecurityRealm.java:644) at hudson.model.User$UserIDCanonicalIdResolver.resolveCanonicalId(User.java:1049) ... The step after recording fingerprints in the job there is the Chuck Norris plugin and that's the last step in the job. 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] [core] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Leandro Lucarella commented on JENKINS-34775 Re: Broken jobs after upgrade to 1.651.2 security update I could find the old version in http://pkg.jenkins-ci.org/debian-stable/ and reverted and all works fine with 1.651.1. 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] [core] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Leandro Lucarella created an issue Jenkins / JENKINS-34775 Broken jobs after upgrade to 1.651.2 security update Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/May/12 6:01 PM Environment: Ubuntu 14.04 Priority: Blocker Reporter: Leandro Lucarella After upgrading to 1.651.2 security update, jobs are getting this error: FATAL: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken java.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken at org.jenkinsci.plugins.GithubSecurityRealm.loadUserByUsername(GithubSecurityRealm.java:644) at hudson.model.User$UserIDCanonicalIdResolver.resolveCanonicalId(User.java:1049) at hudson.model.User.get(User.java:395) at hudson.model.User.get(User.java:364) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:374) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:435) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:350) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:346) at
[JIRA] [github-plugin] (JENKINS-34144) Don't fail the job if setting the GitHub status fails
Title: Message Title Leandro Lucarella commented on JENKINS-34144 Re: Don't fail the job if setting the GitHub status fails Thanks! 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-plugin] (JENKINS-34144) Don't fail the job if setting the GitHub status fails
Title: Message Title Leandro Lucarella created an issue Jenkins / JENKINS-34144 Don't fail the job if setting the GitHub status fails Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin Created: 2016/Apr/11 1:16 PM Priority: Critical Reporter: Leandro Lucarella If setting the commit status fails, for example because of a timeout, an exception is thrown and the job is marked as failed, which I think is not a reasonable option, as there is nothing wrong with the build itself. It would be better to just report the problem in some way but keep the job status intact. Example: Setting commit status on GitHub for https://github.com/some/repo/commit/7304040cd2d63d15cbe922e23fd6dac7ad86bca8 ERROR: Step ‘Set build status on GitHub commit’ aborted due to exception: java.net.SocketTimeoutException: timeout at okio.Okio$3.newTimeoutException(Okio.java:207) at okio.AsyncTimeout.exit(AsyncTimeout.java:261) at okio.AsyncTimeout$2.read(AsyncTimeout.java:215) at okio.RealBufferedSource.indexOf(RealBufferedSource.java:306) at okio.RealBufferedSource.indexOf(RealBufferedSource.java:300) at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:196) at com.squareup.okhttp.internal.http.HttpConnection.readResponse(HttpConnection.java:191) at com.squareup.okhttp.internal.http.HttpTransport.readResponseHeaders(HttpTransport.java:80) at com.squareup.okhttp.internal.http.HttpEngine.readNetworkResponse(HttpEngine.java:906) at
[JIRA] [github-plugin] (JENKINS-20518) inspect github payload and build specific SHAs
Title: Message Title Leandro Lucarella commented on JENKINS-20518 Re: inspect github payload and build specific SHAs Thanks but my java-fu is null to contribute anything (and I'm not planning to get any) and I have a large jenkins installation testing hundreds of projects, so I can't change all my setup to test a completely new plugin. I think I will workaround this problem by using a combination of receiving the github webhook as described in here: http://chloky.com/github-json-payload-in-jenkins/ and then process the payload using a programming language I speak to trigger the build using the trigger URL for the Git 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.
[JIRA] [github-plugin] (JENKINS-20518) inspect github payload and build specific SHAs
Title: Message Title Leandro Lucarella commented on JENKINS-20518 Re: inspect github payload and build specific SHAs The Git plugin already offers a facility to build the exact sha1 that you pass: https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-Pushnotificationfromrepository I was really surprised to find out that the GitHub push trigger only triggers a polling instead of (unconditionally) build the sha1/branch specified by the GitHub webhook payload. 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-plugin] (JENKINS-33974) Add option to verify "secret" token
Title: Message Title Leandro Lucarella created an issue Jenkins / JENKINS-33974 Add option to verify "secret" token Issue Type: Improvement Assignee: Kirill Merkushev Components: github-plugin Created: 2016/Apr/01 9:56 AM Labels: security Priority: Major Reporter: Leandro Lucarella For security reasons, it's quite important for this plugin to support an option to verify a "secret" token. This option was added some time ago, you basically configure a "secret" in the GitHub webhook end, so you know the requests you are receiving is really from GitHub. The GitHub Pull Request Builder plugin (ghprb) already supports it. It would be great if this plugin add support too. Add Comment
[JIRA] [description-setter-plugin] (JENKINS-8447) Add Token Macro expansion
Title: Message Title Leandro Lucarella updated an issue Jenkins / JENKINS-8447 Add Token Macro expansion Change By: Leandro Lucarella Summary: Description setter doesn't expand variables consistently Add Token Macro expansion 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] [description-setter-plugin] (JENKINS-8447) Add Token Macro expansion
Title: Message Title Leandro Lucarella updated an issue Jenkins / JENKINS-8447 Add Token Macro expansion Change By: Leandro Lucarella Issue Type: Bug Improvement 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-plugin] (JENKINS-24291) GitHub plugin to make parameters from webhook data
Title: Message Title Leandro Lucarella commented on JENKINS-24291 Re: GitHub plugin to make parameters from webhook data Also bumping into this, I always thought that the PUSH trigger only (and unconditionally) built whatever the hook payload told jenkins to build, not that the hook just triggered a Git poll. (I just discovered is documented behaviour) 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-29714) infinite polling with variable in branchspec
Title: Message Title Leandro Lucarella commented on JENKINS-29714 Re: infinite polling with variable in branchspec More info, this is how my polling looks when using a parameter for the branch specification: Started on Mar 30, 2016 1:19:00 PM Using strategy: Default [poll] Last Built Revision: Revision ace29d00302d20dddb3763057f31ab40b1fe8b4b (origin/v2.x.x) using GIT_SSH to set credentials cred SSH key > git --version # timeout=10 > git -c core.askpass=true ls-remote -h g...@github.com:some/repo.git # timeout=10 Found 32 remote heads on g...@github.com:some/repo.git [poll] Latest remote head revision on refs/heads/v1.7.x is: 138b74fc9ce8885aefdeabfdf8bc3ecca572d264 - already built by 333 [poll] Latest remote head revision on refs/heads/v1.4.x is: 57d03eb35379098071726699783055535a8bd425 - already built by 338 [poll] Latest remote head revision on refs/heads/v1.17.x is: 22d0d8742bacf4c89602fc98f20017c323cdf7bc - already built by 18 [poll] Latest remote head revision on refs/heads/v1.2.x is: b919d378aac4e503c21b58d940197553f4983344 - already built by 340 [poll] Latest remote head revision on refs/heads/v1.27.x is: fe1052f3b95a5b75be18b45ce41743da900712f9 - already built by 343 [poll] Latest remote head revision on refs/heads/v1.5.x is: 0ae940fecddcd4a5a785e5871e12b200ddfb7bee - already built by 345 [poll] Latest remote head revision on refs/heads/v1.24.x is: 71c050ef5b8fc3430f80cafb27109d34aa103876 - already built by 347 [poll] Latest remote head revision on refs/heads/v1.19.x is: d09a06c871bdc8f518f694877110189258792392 - already built by 349 [poll] Latest remote head revision on refs/heads/v1.26.x is: 1d053f81485174957c38cee420eac1292ceb82ef - already built by 351 [poll] Latest remote head revision on refs/heads/master is: 3a9bf5071b66bd78b2e90984b88dba22ffea489e - already built by 336 [poll] Latest remote head revision on refs/heads/v1.25.x is: 912e94dbb7f9bdc4ceec75a9c7e56cb1dbbbce75 - already built by 352 [poll] Latest remote head revision on refs/heads/v1.23.x is: b7919967ce1e152ef4656b7b4866ba14b8ec - already built by 357 [poll] Latest remote head revision on refs/heads/v1.6.x is: fababe9cd990e1867e28f501b0e91faf1e920a5a - already built by 359 [poll] Latest remote head revision on refs/heads/v1.18.x is: 987f8c23304b99a6377cae63c7a9a7b5051f4e62 - already built by 361 [poll] Latest remote head revision on refs/heads/v1.1.x is: 4008675d54b10bafd675a25ba093190697af867f - already built by 365 [poll] Latest remote head revision on refs/heads/v1.22.x is: 2e47914dfa42cb595731b264cbecc277620aced0 - already built by 19 [poll] Latest remote head revision on refs/heads/v1.13.x is: cf834f5d3968d8b3996025fc1eb570d17b6a3083 Done. Took 2.4 sec Changes found refs/heads/v1.13.x is not detected as being already built, but instead of building that reference, the last reference is built (ace29d00302d20dddb3763057f31ab40b1fe8b4b (origin/v2.x.x)), so on the next polling the same happens, refs/heads/v1.13.x is detected as not being built and again the last version built gets rebuilt, getting into an infinite rebuilding loop. And this is how it looks when just leaving the branch specification empty: Started on Mar 30, 2016 12:59:00 PM Polling SCM changes on master Using strategy: Default [poll] Last Built Revision: Revision ace29d00302d20dddb3763057f31ab40b1fe8b4b (origin/v2.x.x) > git rev-parse
[JIRA] [description-setter-plugin] (JENKINS-30195) Option for appending an unique descriptions only
Title: Message Title Leandro Lucarella commented on JENKINS-30195 Re: Option for appending an unique descriptions only BTW, the current state is not even what the help message states for matrix jobs: "Also set the description on a multi-configuration build. The first description found for any of the invididual builds will be used as description for the multi-configuration build. " 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] [build-name-setter-plugin] (JENKINS-33876) Add ability to set build description too
Title: Message Title Leandro Lucarella created an issue Jenkins / JENKINS-33876 Add ability to set build description too Issue Type: New Feature Assignee: Lev Mishin Components: build-name-setter-plugin Created: 2016/Mar/29 2:53 PM Priority: Minor Reporter: Leandro Lucarella It would be nice to be able to set the job description too, as some information is too much to include in the name (and sometimes is nice to include links too). For example, the GitHub Pull Request Builder plugin sets the description to have the title and a link to the pull request. I would like to do something similar to normal builds (not triggered by a pull request), to include a link to the branch and the specific commit in the GitHub project. The Description Setter Plugin is just too limited to do this, this plugin is much more flexible and I have the feeling it should be not a radical change to just set one extra field, this is why I do this feature request instead of suggesting to improve the Description Setter Plugin. Thanks! Add Comment
[JIRA] [git-plugin] (JENKINS-29714) infinite polling with variable in branchspec
Title: Message Title
Leandro Lucarella commented on JENKINS-29714
Re: infinite polling with variable in branchspec
If I do a manual build of the branch that keeps triggering the build (by setting my parameter $ {ref}
to that branch), then that particular branch build is not triggered anymore by the pooling, I have to repeat the process with all the "offending" branches, and then the job seems to work fine.
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-29714) infinite polling with variable in branchspec
Title: Message Title
Leandro Lucarella commented on JENKINS-29714
Re: infinite polling with variable in branchspec
I'm also affected by this. My use case is exactly as described by Kanstantsin Shautsou in https://issues.jenkins-ci.org/browse/JENKINS-29714?focusedCommentId=233448=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-233448 but I use $ {ref}
in the branchspec field (and the default value of parameter "ref" is an empty value).
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-33258) Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user
Title: Message Title Leandro Lucarella commented on JENKINS-33258 Re: Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user Anyway, I'm fine if you want to close this as invalid or cantreproduce, as once the browser was restarted I never experienced this again. 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-33258) Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user
Title: Message Title Leandro Lucarella commented on JENKINS-33258 Re: Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user But thanks for the link, I've made my own gitignore rules, I'll check if I missed anything. 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-33258) Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user
Title: Message Title Leandro Lucarella commented on JENKINS-33258 Re: Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user I am This was very early in the stage of the move, I just copied a couple of jobs to make sure I installed all the necessary plugins, etc. Once everything looked fine, I checked out the whole config files I have in git, and then it happened. 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-33258) Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user
Title: Message Title Leandro Lucarella commented on JENKINS-33258 Re: Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user I'm using the versions you listed, but I experienced the problem before the update (I disabled auth and updated hoping for the problem to go away). Is hard to tell the changes in JENKINS_HOME unfortunately, I'm moving one jenkins instance to another but starting for a clean setup, not doing a complete move, so I added a bunch of jobs configuration files and maybe other configuration files too. I saved the previous JENKINS_HOME before messing with it, and restoring the old folder didn't fix the problem. I only found out it was a browser related issue because another person told me he didn't have any problems with the server when I told him about this issue. 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-33258) Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user
Title: Message Title Leandro Lucarella commented on JENKINS-33258 Re: Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user It looks like there's a browser component on this issue, it works fine on a private window and a browser restart fixed it. 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-33258) Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user
Title: Message Title Leandro Lucarella created an issue Jenkins / JENKINS-33258 Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user Issue Type: Bug Assignee: Sam Gleske Components: github-oauth-plugin Created: 02/Mar/16 1:33 AM Environment: Jenkins 1.642.2, Ubuntu 14.04, plugin version 0.22.3 Priority: Blocker Reporter: Leandro Lucarella Hi, I'm suddenly getting this error and can't use jenkins at all with OAuth plugin. The OAuth applications is set up correctly, and the client secret and ID are set into jenkins config. I did some changes in the jenkins data directory, so it might be my fault that this is broken, but I fail to make it work again unless I disable security completely in Jenkins. Any help to debug this would be appreciated. The error I get on every Jenkins URL (BTW, I revoked access to my user to this App, and I don't even get GitHub login page when going to Jenkins). java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user at
[JIRA] [cloudbees-folder-plugin] (JENKINS-33095) Upgrade to folder 5.2.1 + matrix-auth 1.3 results in dead Jenkins
Title: Message Title Leandro Lucarella commented on JENKINS-33095 Re: Upgrade to folder 5.2.1 + matrix-auth 1.3 results in dead Jenkins Jenkins 1.642.1 killed in here by the upgrade. 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-16350) "logout" link doesn't work
Title: Message Title Leandro Lucarella commented on JENKINS-16350 Re: "logout" link doesn't work Yup, not really an option for private Jenkins instances... 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-16350) "logout" link doesn't work
Title: Message Title Leandro Lucarella commented on JENKINS-16350 Re: "logout" link doesn't work I understand the technical details, why you are really logging out and re-logging in inmediately. But there is a usability issue. The user is not aware of this and it shouldn't be. Can the login then have some confirmation about using the GitHub OAuth credentials to actually log-in? In that case when you logout you'll be asked again if you really want to use your GitHub OAuth credentials to re-log in. 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-27843) Exception when enabling Use Github repository permissions
Leandro Lucarella created JENKINS-27843 Exception when enabling Use Github repository permissions Issue Type: Bug Assignee: Sam Kottler Attachments: j.png Components: github-oauth-plugin Created: 08/Apr/15 11:43 AM Description: I get this exception when enabling the "Use Github repository permissions" option for any non-admin user in the main page. Job result pages seem to work. javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.596.2.jar!/hudson/model/View/sidepanel.jelly:75:50: st:include java.lang.NullPointerException at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:813) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at
[JIRA] [github-oauth-plugin] (JENKINS-27844) Improve Use Github repository permissions
Leandro Lucarella created JENKINS-27844 Improve Use Github repository permissions Issue Type: Bug Assignee: Sam Kottler Components: github-oauth-plugin Created: 08/Apr/15 11:48 AM Description: The current option "Use Github repository permissions" says: If checked will use github repository permissions to determine jenkins permissions for each project. Public projects - all authenticated users can READ. Only collaborators can BUILD, EDIT, CONFIGURE or DELETE. Private projects, only collaborators can READ, BUILD, EDIT, CONFIGURE or DELETE For private repos there are 3 access levels: pull (read) access, push (write) access and admin access. It would be much better to give people will pull access READ permission, people with push access READ/BUILD permission and READ, BUILD, EDIT, CONFIGURE or DELETE only to admins. Environment: Jenkins ver. 1.596.2, Ubuntu 12.04 Project: Jenkins Priority: Minor Reporter: Leandro Lucarella This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Leandro Lucarella commented on JENKINS-25127 Hook uninstalled if job is in a subfolder I tested the PR and the re-register button seems to work fine, thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Leandro Lucarella commented on JENKINS-25127 Hook uninstalled if job is in a subfolder Yes, at least I tried with one job to manually save it and the hook was installed and not removed afterward. I'll try again, saving a couple more jobs manually, and report back, just in case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Leandro Lucarella commented on JENKINS-25127 Hook uninstalled if job is in a subfolder I tried with a couple more jobs to save them manually and the hooks were properly registered and never removed again. Is only the script to save all the jobs in a batch that doesn't work for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Leandro Lucarella commented on JENKINS-25127 Hook uninstalled if job is in a subfolder Thanks a lot! The script have worked (I got the expected println() output) but no re-registration of hooks to GitHub happened :-/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Leandro Lucarella commented on JENKINS-25127 Hook uninstalled if job is in a subfolder I tried the script but I get this error: groovy.lang.MissingPropertyException: No such property: GitHubPushTrigger for class: Script1 I don't know anything about groovy or java, that means I need an import? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Leandro Lucarella commented on JENKINS-25127 Hook uninstalled if job is in a subfolder What am I looking for in this log? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Leandro Lucarella commented on JENKINS-25127 Hook uninstalled if job is in a subfolder Nice! ETA for a release with this fix? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Leandro Lucarella commented on JENKINS-25127 Hook uninstalled if job is in a subfolder Oh, I see 1.11.1 is out, thanks! Is there any way to tell all the jobs to re-register in GitHub? Right now the only way I could find to do this is to go to each jobs's config and save it again, which is a bit impractical when you have many jobs. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [ghprb] (JENKINS-24954) Test PASSed comments added even if Published Jenkins URL
Leandro Lucarella commented on JENKINS-24954 Test PASSed comments added even if Published Jenkins URL Cool! Thanks a lot! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [ghprb] (JENKINS-24954) Test PASSed comments added even if Published Jenkins URL
Leandro Lucarella commented on JENKINS-24954 Test PASSed comments added even if Published Jenkins URL I didn't understand very well what you are saying above, David. What I want is to make comments only if setting the github commit status fail. I guess for that, the official way to do it (and what worked before) is to have the "Published Jenkins URL" empty, "Use comments to report results when updating commit status fails" checked and the passed and failed messages with some text. Right now with that configuration I get always a message, even when the statuses are being set correctly (at least I can see them in GitHub). So, what I'm doing now (emptying the failed and passed messages text) is only a hack and I guess it will make that if setting the statuses ever fail, I won't get any comments either. Right? This is not what I want, is just a workaround so I don't get spammed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [ghprb] (JENKINS-24954) Test PASSed comments added even if Published Jenkins URL
Leandro Lucarella reopened JENKINS-24954 Test PASSed comments added even if Published Jenkins URL I'm reopening for now, since I don't think this is not an issue, something changed between 1.16 and 1.16-1 that made this plug-in, at least, behave differently. Change By: Leandro Lucarella (16/Oct/14 11:57 AM) Resolution: NotADefect Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [ghprb] (JENKINS-24954) Test PASSed comments added even if Published Jenkins URL
Leandro Lucarella commented on JENKINS-24954 Test PASSed comments added even if Published Jenkins URL I can confirm the workaround WORKS (emptying the text to send in the comments). Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Leandro Lucarella commented on JENKINS-25127 Hook uninstalled if job is in a subfolder I don't have a Java development environment, but I would be very much interested in testing a fix if someone can provide it This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [ghprb] (JENKINS-24954) Test PASSed comments added even if Published Jenkins URL
Leandro Lucarella commented on JENKINS-24954 Test PASSed comments added even if Published Jenkins URL I can confirm it's NOT fixed in 16-3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Leandro Lucarella created JENKINS-25127 Hook uninstalled if job is in a subfolder Issue Type: Bug Assignee: Unassigned Components: github Created: 13/Oct/14 4:06 PM Description: After I started using the CloudBees Folders Plugin and moving jobs into folders, I noticed when I pushed stuff to github, builds were no longer triggered. I checked in GitHub and the Jenkins plugin was not enabled. I go to the job, save it again (the option "Build when a change is pushed to GitHub" is always checked and is the only method to trigger a build that's activated) and I see the hook is created, but after a minute or 2, it gets removed again. GitHub security log says the removal request comes from the Jenkins server. Looking at the source code, I see where hooks are being removed: https://github.com/jenkinsci/github-plugin/blob/49bc59d79707808d73eb0f9d5c97996fd5525d08/src/main/java/com/cloudbees/jenkins/Cleaner.java Activating the log for com.cloudbees.jenkins.Cleaner I can definitely see it's Jenkins the one removing the hooks. Why is considering jobs inside subfolders as "not interesting" I have no idea. Looking at the "GitHub Hook Log" for a top-level project, I see something like this: Last GitHub Push Started on Oct 13, 2014 3:21:08 PM Polling SCM changes on master Using strategy: Default poll Last Built Revision: Revision ae6386642259cb1b675730fbce96deaa29d3a369 (origin/master) git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repositories git config remote.origin.url g...@github.com:sociomantic/git-hub.git # timeout=10 Fetching upstream changes from g...@github.com:sociomantic/git-hub.git git --version # timeout=10 using GIT_SSH to set credentials GitHub jenkins-admin git fetch --tags --progress g...@github.com:sociomantic/git-hub.git +refs/heads/:refs/remotes/origin/ Polling for changes in Seen branch in repository origin/master git log --full-history --no-abbrev --format=raw -M -m --raw ae6386642259cb1b675730fbce96deaa29d3a369..7618cac3f33deb84868332acc64572b60d7adf7e # timeout=10 Done. Took 3.4 sec Changes found (I don't know why is it polling anything in the first place because Polling is not enabled) For a job in a subfolder, I see this log instead: Environment: Jenkins ver. 1.565.3, GitHub plugin 1.9.1, CloudBees Folders Plugin 4.6.1 Project: Jenkins Priority: Critical Reporter: Leandro Lucarella This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Leandro Lucarella updated JENKINS-25127 Hook uninstalled if job is in a subfolder Change By: Leandro Lucarella (13/Oct/14 4:09 PM) Description: AfterIstartedusingtheCloudBeesFoldersPluginandmovingjobsintofolders,InoticedwhenIpushedstufftogithub,buildswerenolongertriggered.IcheckedinGitHubandtheJenkinspluginwasnotenabled.Igotothejob,saveitagain(theoptionBuildwhenachangeispushedtoGitHubisalwayscheckedandistheonlymethodtotriggerabuildthatsactivated)andIseethehookiscreated,butafteraminuteor2,itgetsremovedagain.GitHubsecuritylogsaystheremovalrequestcomesfromtheJenkinsserver.Lookingatthesourcecode,Iseewherehooksarebeingremoved:https://github.com/jenkinsci/github-plugin/blob/49bc59d79707808d73eb0f9d5c97996fd5525d08/src/main/java/com/cloudbees/jenkins/Cleaner.javaActivatingthelogforcom.cloudbees.jenkins.CleanerIcandefinitelyseeitsJenkinstheoneremovingthehooks.WhyisconsideringjobsinsidesubfoldersasnotinterestingIhavenoidea. LookingattheGitHubHookLogforatop-levelproject,Iseesomethinglikethis:---LastGitHubPushStartedonOct13,20143:21:08PMPollingSCMchangesonmasterUsingstrategy:Default[poll]LastBuiltRevision:Revisionae6386642259cb1b675730fbce96deaa29d3a369(origin/master)gitrev-parse--is-inside-work-tree#timeout=10FetchingchangesfromtheremoteGitrepositoriesgitconfigremote.origin.urlg...@github.com:sociomantic/git-hub.git#timeout=10Fetchingupstreamchangesfromg...@github.com:sociomantic/git-hub.gitgit--version#timeout=10usingGIT_SSHtosetcredentialsGitHubjenkins-admingitfetch--tags--progressg...@github.com:sociomantic/git-hub.git+refs/heads/*:refs/remotes/origin/*PollingforchangesinSeenbranchinrepositoryorigin/mastergitlog--full-history--no-abbrev--format=raw-M-m--rawae6386642259cb1b675730fbce96deaa29d3a369..7618cac3f33deb84868332acc64572b60d7adf7e#timeout=10Done.Took3.4secChangesfound---(IdontknowwhyisitpollinganythinginthefirstplacebecausePollingisnotenabled)Forajobinasubfolder,Iseethisloginstead:--- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [ghprb] (JENKINS-24954) Test PASSed comments added even if Published Jenkins URL
Leandro Lucarella commented on JENKINS-24954 Test PASSed comments added even if Published Jenkins URL I tried to downgrade but jenkins hanged forever on restart. I had to manually remove the plugin file and resintall, but the latest version, so I'm still having this problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [ghprb] (JENKINS-24954) Test PASSed comments added even if Published Jenkins URL
Leandro Lucarella commented on JENKINS-24954 Test PASSed comments added even if Published Jenkins URL Not for me, I killed -9 all the java processes around and jenkins wouldn't restart anyway :S Now that I removed the plugin manually and reinstalled it, I don't even have the option to downgrade anymore... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [ghprb] (JENKINS-24954) Test PASSed comments added even if Published Jenkins URL
Leandro Lucarella created JENKINS-24954 Test PASSed comments added even if Published Jenkins URL Issue Type: Bug Assignee: Honza Brázdil Components: ghprb Created: 01/Oct/14 7:08 PM Description: After upgrading from ghprb 1.16 to 1.16-1 I started getting comments on Pull Requests with "Test PASSed", even when the global option "Published Jenkins URL" is empty, which is supposed to disable those comments. I even disabled the option "Use comments to report results when updating commit status fails" in case the plugin was getting some error while updating the status, but it didn't change anything. Right now I can't find any way to disable those comments. Environment: Jenkins 1.565.2, ghprb 1.16-1 Project: Jenkins Priority: Major Reporter: Leandro Lucarella This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-23673) Can't configure private projects I own when using Use Github repository permissions option
Leandro Lucarella created JENKINS-23673 Cant configure private projects I own when using Use Github repository permissions option Issue Type: Bug Affects Versions: current Assignee: Sam Kottler Components: github-oauth Created: 03/Jul/14 5:27 PM Description: Maybe I'm not understanding this feature properly, but I have an user with "admin access" in GitHub for some projects and I can't configure all of those projects jobs in Jenkins. How does this plug-in checks is a job is associated to a particular GitHub project? By the "GitHub project" configuration? I noticed the only project I can configure is the only one that is public, all private projects are not given the configure option, even if I have admin access to all of them. Environment: Jenkins 1.554.3 with about 35 jobs. Project: Jenkins Priority: Major Reporter: Leandro Lucarella This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-23672) Jobs page load takes ages when Use Github repository permissions is checked
Leandro Lucarella created JENKINS-23672 Jobs page load takes ages when Use Github repository permissions is checked Issue Type: Bug Affects Versions: current Assignee: Sam Kottler Components: github-oauth Created: 03/Jul/14 5:22 PM Description: When "Use Github repository permissions" is checked, loading the list of jobs (main jenkins page) takes ages (around a minute). When I uncheck that option, it takes only around a second. Environment: Jenkins 1.554.3 with about 35 jobs. Project: Jenkins Priority: Major Reporter: Leandro Lucarella This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-20883) Can't publish arbitrary URLs
Leandro Lucarella commented on JENKINS-20883 Cant publish arbitrary URLs But I don't want to give anonymous the "view status" permission globally I don't even see that option when using the github-oauth plugin for authentication, I only see "Grant READ permissions for Anonymous Users" which might be the same. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Leandro Lucarella commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder OK, thanks for the advice. Since what we really need is GitHub integration, and I don't see a lot about it in cloudbees website, I'd be more inclined in finding a freelance jenkins devel that might be interested in addressing a few issues we have. I'll contact cloudbees anyway, you never know... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Leandro Lucarella commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder There is also a possibility to provide some funding to fix this, is the FreedomSponsors.org sponsoring really used? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Leandro Lucarella commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder I looked at JENKINS-21980 and even when it looks similar, the effects are different. GitHub report no changes, but they mention no problems with the checkout itself. So I wonder if is the same root cause for this or not. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Leandro Lucarella commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder BTW, guidance on how to fix this would be appreciated. I'm willing to spend some time on this, but I have no idea about Jenkins internals or how the plugins hooks to the different jenkins stages. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-22035) Add Repository based authorization
Leandro Lucarella commented on JENKINS-22035 Add Repository based authorization Seems like the PR was merged already, any ETA for a release? 8-) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Leandro Lucarella commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder We used the EnvInject plugin to run some tests before the repo is checked out. When building multiple configurations, there seems to be 3 git repositories, the one in the regular workspace that is checked out by the main job, and then for each configuration, another repo living in workspace/VAR/VALUE, where the project is really built. We suspect those configuration-specific copies are not updated for some reason, and thus origin/pr/XXX/merge points to an old commit that is not present in that particular repo anymore. We wanted to force a git fetch on those repos before the checkout, but the problem is bofore the check those repo don't even exist! It looks like jenkins do a clone for them or something. Another weird thing is after doing this experimentation with EnvInject, the problematic PR got "fixed". We suspect that something might have been cleaned when the pre-checkout commit failed, and the checkout was never done, but all these are just wild guesses. We'll continue to investigate this as much as possible, but all points to some conflict with multiple configuration builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Leandro Lucarella commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder Also, I think this problem only happens when a PR is being tested and there is a push -f in the same PR, so a new build is queued. After that happens, the build seems to stay broken. Any idea about how this push -f while the PR is being tested can end up in this situation? Is any information about the hash being stored somewhere that is read then by the queued build for the same PR? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Leandro Lucarella commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder I can reproduce this easily now, is that, pushing --force to a PR that's being tested already in Jenkins. A simple test is just have a dummy project, which just a build script that is a sleep 60. Then create a PR, wait until jenkins runs the job to build it, while is at it, do a git rebase --force HEAD^ to the project and push --force to the PR branch and boom! If configurations are really a problem or not needs to be confirmed still, I'll do that as soon as possible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Leandro Lucarella commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder I think the pr builder plugin should just do the git fetch with the pull request references and then just use the symbolic name of the references (origin/pr/N/merge) instead of using any hash. But I don't know exactly how is the interaction between this plugin and the git-plugin, I'm just thinking in terms of plain git commands. I really don't see why any of the plugins should use any numeric old hash. I'll do my best to try to reproduce this with a Java test case, but I can't promise anything because my Java-fu is practically non-existant (even when Java as a language is easy, the thousands layers of libraries are not easy to grasp at all :S). Also, I'll take another look at JENKINS-21980 now that I have a better idea of where the issue is. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Leandro Lucarella commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder BTW, the checkout fails because for some reason is trying to checkout an old for that pull request (that was force-pushed). Sometimes it works, sometimes it doesn't. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Leandro Lucarella commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder Yeah, that's what JENKINS-21980 seems to be suggesting, that Jenkins remembers the hash of the last build (now detached) to check if there are changes or not. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [ghprb] (JENKINS-20436) Allow automatic merge after successful build
Leandro Lucarella commented on JENKINS-20436 Allow automatic merge after successful build Merge or rebase, to match this issue: https://issues.jenkins-ci.org/browse/JENKINS-20435 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] (JENKINS-20845) Github Authorization Settings, users in Participant in Organization not given READ
Leandro Lucarella commented on JENKINS-20845 Github Authorization Settings, users in Participant in Organization not given READ Oh, so THAT was the problem! All the members in my organization are not public, once I changed them to be public it worked as expected! So I'm not experiencing this issue anymore. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] [github-oauth] (JENKINS-21331) Improve usage of github permissions to be able to assign individual permissions to users or teams
Leandro Lucarella created JENKINS-21331 Improve usage of github permissions to be able to assign individual permissions to users or teams Issue Type: New Feature Affects Versions: current Assignee: Sam Kottler Components: github-oauth Created: 10/Jan/14 4:04 PM Description: Permissions granularity when using the plugin is extremely limited when using the plugin. It would be nice if the plugin could also provide some kind of matrix to set permissions to individual users or github teams (ideally). Also it would be extremely useful if you could link any job to a github project and map github permissions to job permissions. Users with pull access should only see the results, users with push access should also be able to execute the job and users with admin access should be able to edit the job's configuration. Project: Jenkins Labels: github permissions Priority: Major Reporter: Leandro Lucarella This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] [github-oauth] (JENKINS-20845) Github Authorization Settings, users in Participant in Organization not given READ
Leandro Lucarella commented on JENKINS-20845 Github Authorization Settings, users in Participant in Organization not given READ Vote it! BTW, for me this is a blocker. Is there any workaround besides manually setting everybody as admins? For me adding permission to any random user that authenticates to jenkins using github is not an option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
