Request for comments: Copyartifact 2.0
Hello all. I plan to start to develop Copyartifact 2.0 with major changes which may no longer preserve compatibility with 1.X. I request comments, advices, and requests for that. You can also comment on JIRA: https://issues.jenkins-ci.org/browse/JENKINS-24892 Planned features of Copyartifact 2.0: * Verbose option. * Add an option to have outputs like build XXX is skipped for unstable. * There are often JIRA issues the build wasn't properly selected, but there's no way to diagnose that. * Supports ArtifactManager introduced in Jenkins 1.532 * This allows copyartifact work with other plugins archiving artifacts such as Compress Artifacts Plugin. * Supports Workflow plugin. * I expect the work of Tom Fennely: https://github.com/jenkinsci/copyartifact-plugin/pull/43 * Requires SimpleBuildStep introduced in Jenkins 1.577. * Runtime permission checks. * 1.X performs permission checks only when projects to copy from are specified with variables. This is misleading, users are often confused, and that results in many JIRA issues. * Users are expected to configure authorization of job executions with QueueItemAuthenticator introduced in Jenkins 1.520. * BuildFilter-based configuration * Copyartifact provides BuildSelector and BuildFilter as mechanisms to select a build to copy from. * 1.X mainly uses BuildSelectors. * BuildFilter-based configuration would allow more flexible build specifications such as: the last completed build that is unstable or more AND a downstream of build XXX AND its parameter FOO is BAR OR BAZ. Regards, ikedam. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Signing Artifacts
Hi, I want to publish a new release of the gradle-jpi-plugin. Previous release artifacts of that plugin have been signed with some GPG key, e.g. http://repo.jenkins-ci.org/public/org/jenkins-ci/tools/gradle-jpi-plugin/0.5.0/ Signing artifacts seems to be a good idea in general. Is there some kind of policy for that? Shall I use my own key or is there a special Jenkins key? Daniel -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
commit access to configuration slicing plugin
Hi, Can I be provided with commit access to the configuration slicing plugin github repository please, in line with what is suggested in https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-Makingchangestoexistingplugins? I’ve contacted the previous maintainer, and he’s confirmed that he’s no longer maintaining the plugin, so I’d just like to merge in the current pull requests and make a release for them. The repository is at https://github.com/jenkinsci/configurationslicing-plugin and my github id is ninian. thanks Ninian -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: New Jenkins plugin hosting request; Ratchet-plugin
In my opinion, the plugin's name is too vague. Ratchet and Ratcheting words are just the slang without a valuable info about the real functionality (build log analysis?). Could you consider the plugin's renaming? Several proposals regarding pom.xml - groupId: What about com.mattersight.jenkinsci.plugins? - it's preferable to avoid uppercase letters in artifactId пятница, 26 сентября 2014 г., 23:02:47 UTC+4 пользователь Wiering, Nathan написал: Dear Jenkins dev team, I have been developing a ratcheting plugin for Jenkins for my company (Mattersight Corp.) that we would like to have hosted on the Jenkins Github. The goal of this plugin is to provide a means to ratchet on code coverage results- causing a build to fail if it drops below a threshold. GitHub plugin name: Ratchet-plugin Github id: ntw1103 Github project to be forked: https://github.com/ntw1103/Ratchet Please let me know if there is anything else required. Thanks, Nathan Wiering -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ANN] CloudBees is looking for Jenkins developers support engineers in the US
Thanks Richard, let's take this off list. 2014-09-26 21:23 GMT-07:00 Richard Lavoie lavoie.rich...@gmail.com: Hi Kohsuke, That could be a very good opportunity I am interested in but I'm currently based near Montreal, Canada. I'm currently the maintainer of the selenium plugin, even though I haven't had time lately to do any fix because of lack of personal time, pregnant girlfriend, commuting and the company I'm currently work for doesn't have an interest in it so... Not an excuse but I do currently lack free time. Are there any plans for CloudBees to open an office in Montreal or even Canada ? Would they hire someone outside from U.S. and working remote ? Thanks fot the opportunity offer, Richard Lavoie On 2014-09-26, at 21:39, Kohsuke Kawaguchi kkawagu...@cloudbees.com wrote: (I hope this doesn't come across as a spam, and I think we've had this kind of emails in the past) CloudBees is looking for full-time Jenkins developers support engineers working for us in the U.S. For the developer role, we are looking for somebody who already knows Jenkins code and have some experiences writing plugins. Any experience running Jenkins deployments for large teams would be plus. For the support engineer role, experience hacking code is less important, but we'd be looking for keen problem solving skills. As we all know, troubleshooting Jenkins is often like solving a mystery, and you need a great detective skills --- attention to details, logical reasoning skills, that sort of things. In either case, you'll be working with people who you hopefully already know: myself, Jesse Glick, Stephen Connolly, Nicolas De Loof, Steven Christou, Robert Sandell, ... Those folks make me feel inferior every single day, and I hope you'd see that as a privilege like I do. Ideally we'd love people who can commute to one of our offices --- Los Altos CA, or Richmond VA. But if you are interested, please drop me a note regardless of where you are. -- Kohsuke Kawaguchi -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Kohsuke Kawaguchi -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: New Plugin Request
Hello Anthony, Are there any other possible use-cases excepting the pyblishing to your server? If no, what about changing the plugin's name to codedx-publisher? Best regards, Oleg Nenashev пятница, 26 сентября 2014 г., 22:50:58 UTC+4 пользователь Anthony DeMartini написал: Greetings, I’m with the CodeDx development team at Secure Decisions ( http://codedx.com/) and we are developing a plugin for Jenkins to publish builds to our software assurance analysis tool. Our current plugin is located here: https://github.com/secdec/codedx-jenkins-plugin and my github handle is ademartini. We have chosen a groupid of org.jenkins-ci.plugins and an artifactid of codedx. From the documentation it looks like the next step would be to move our code into the Jenkins github area. We are not necessarily opposed to this but want to know if there are any limitations if we were to keep our code in its current github repo. Would we still be able to publish it and have a wiki page and be listed as an official plugin? Thank You, Anthony DeMartini Senior Software Engineer Applied Visions, Inc. 631-759-3914 -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Discussion: Refactoring of JENKINS project in JIRA
Update on Components refactoring: - All required commands have been added to Jenkins IRC Bot (see https://wiki.jenkins-ci.org/display/JENKINS/IRC+Bot) - Major core components have been renamed and merged (see the status on https://wiki.jenkins-ci.org/display/JENKINS/2014+JIRA+Components+Refactoring) - Plugins modifications: in progress (background activity); https://issues.jenkins-ci.org/browse/INFRA-147 would be very useful, but a public announcement is required пятница, 5 сентября 2014 г., 11:55:02 UTC+4 пользователь Tom Fennelly написал: Hi Richard. Would be no problem adding that - would be the same basic process. I think we need to be careful not to add to many Important notices as that may just lead to people not reading any of them. On Thursday, September 4, 2014 3:02:28 PM UTC+1, Richard Mortimer wrote: Hi, On 04/09/2014 13:22, Tom Fennelly wrote: At yesterdays governance meeting on #jenkins we talked about configuring JIRA to provide some helpful text wrt the Components and Labels fields to help people file issues more consistently. We talked about doing it using Javascript hacks. I installed a trial JIRA and was able to configure the fields easily enough. I moved the Components and Labels fields together on the form and configured some bright ( ;) ) help text on each field. * Here's a screenshot of what it can look like https://www.dropbox.com/s/kn7mc5qzyk9gfwn/Screenshot%202014-09-04%2013.04.05.png?dl=0. * Here's the JIRA: https://issues.jenkins-ci.org/browse/INFRA-123 Looks good to me. Possible text edits aside, I think this should help. Along similar lines... Is it possible to add some text to remind people that JIRA is intended for reporting bugs and rfes. There is a steady stream of people who seem to report their setup/configuration questions in JIRA rather than asking via email or IRC. Maybe add some text to the Issue Type field along the following lines to point people at the proper support forums: Important: This issue tracker is intended to track bugs and enhancements to Jenkins. Questions regarding configuration and operation of Jenkins should be directed towards jenkins...@googlegroups.com or the #jenkins channel (http://jenkins-ci.org/content/chat) on IRC. Regards Richard -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Request to publish a Jenkins plug-in
Hi Jenkins Dev team, I am with the Rational Team Concert(RTC) Development team in IBM (www.ibm.com, www.jazz.net). We are developing a plugin which will integrate Jenkins Builds using Git as Source control to RTC Work items and builds. We would like to publish the plugin at jenkins-ci.org. Here are the details related to plugin Plugin Name: Team Concert Git Plugin Github Repository: https://github.com/clkkishore/teamconcert-git-plugin Github id: clkkishore Plugin Description: Integrates Jenkins with Rational Team Concert for Jenkins Builds which use Git as source control. This plugin will create traceability links from a Jenkins build to RTC work items and build result. Can someone please clone this to jenkinsci and provide me access for the same. Thanks In advance, Regards, Kishore PS: Currently the project https://github.com/clkkishore/teamconcert-git-plugin contains only a readme file will add the sources once the repository is cloned into jenkinssci space. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Google OAuth Plugin does not load scope
I assume you are building a plugin to access this API, using an OAuth2
credential? Otherwise, I'll probably need some more context on how you
plan to wire things up...
If you are building such a plugin you should look at how the Google Cloud
Storage plugin specifies its OAuth2 scope requirement:
https://github.com/jenkinsci/google-storage-plugin/blob/master/src/main/java/com/google/jenkins/plugins/storage/GoogleCloudStorageUploader.java#L51
Putting an appropriately constructed @RequiresDomain on any describable
(e.g. Publishers) will make the error you are seeing go away. As I said
(more tersely) before, we scan for these annotations to dynamically
populate the pertinent set of scopes for installed plugins.
Specifically, you are going to want to define:
public class ChromeWebStoreScopeRequirement extends
GoogleOAuth2ScopeRequirement {
which returns the scope you list, similar to StorageScopeRequirement
https://github.com/jenkinsci/google-storage-plugin/blob/master/src/main/java/com/google/jenkins/plugins/storage/StorageScopeRequirement.java,
then annotate something like this:
@RequiresDomain(value = ChromeWebStoreScopeRequirement.class)
public class ChromeWebStorePublisher extends Recorder {
or maybe I am completely misunderstanding your intent... Hope that helps.
-M
On Fri, Sep 26, 2014 at 9:51 AM, Calvin cc...@pingidentity.com wrote:
Hi Matt,
I have both the Google OAuth Plugin as well as the OAuth Credential Plugin
installed and enabled. The scope I'm needing specifically from the Google
OAuth Plugin is, scope=https://www.googleapis.com/auth/chromewebstore to
use this API, https://developer.chrome.com/webstore/using_webstore_api
https://lh4.googleusercontent.com/-JiykxSQwKIg/VCWZhx-P5UI/AeA/tq0xSrvd-mQ/s1600/Screen%2BShot%2B2014-09-26%2Bat%2B9.48.06%2BAM.png
On Friday, September 26, 2014 9:35:35 AM UTC-7, Matthew Moore wrote:
What plugins do you have installed that require OAuth? This plugin
dynamically determines the set of OAuth scopes that might be required by
installed plugins, to allow you to pick and choose which should be allowed
for a given credential.
Try installing google-storage-plugin, for example, and the storage scope
should show up where you currently have that error message.
LMK if you are expecting something to show up, which isn't.
-M
On Thu, Sep 25, 2014 at 11:04 PM, Calvin cc...@pingidentity.com wrote:
Just installed the Google OAuth Plugin into Jenkins in addition to
having the OAuth Credential Plugin, and upon configuring a new credential
domain neither plugins load the Google OAuth scopes. Anybody experience
this before?
https://lh5.googleusercontent.com/-h5XOtXgqPrM/VCUB1xLwcdI/Adw/VgS-687r3c4/s1600/Screen%2BShot%2B2014-09-25%2Bat%2B5.33.34%2BPM.png
--
You received this message because you are subscribed to the Google
Groups Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Matthew Moore
DI/Docker (aka Convoy)
Developer Infrastructure @ Google
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an
email to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Matthew Moore
DI/Docker (aka Convoy)
Developer Infrastructure @ Google
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
