Yesterday's security advisory

Hi everyone, We now had the situation where the number of vulnerabilities far exceeded what the security team could handle. https://jenkins.io/security/advisory/2017-04-10/ As previously discussed on this list, I've suspended distribution of plugins that are currently vulnerable.

Re: Bug Triage "Team"

> On 10.04.2017, at 22:44, Slide wrote: > > if you are interested! I am. -- 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

Re: Wiki Page Layout

> On 10.04.2017, at 00:05, Oleg Nenashev wrote: > > I am not sure that newly introduced layouts will work correctly there It doesn't even work currently, because the plugin info macro is supposed to be removed from the main content :-( -- You received this message

Re: Removing unsafe old versions of plugins from update sites

> On 10.04.2017, at 00:05, Daniel Beck <m...@beckweb.net> wrote: > > Only since 2.40 and 2.32.2, so in my example in the original email, there's > plenty of instances without a warning, that still would get the plugin. In fact, I expect we'll still operate update sites for r

Re: Removing unsafe old versions of plugins from update sites

> On 10.04.2017, at 00:01, Oleg Nenashev wrote: > > I think that the minimal requirement from the community side is to have the > Security fixes applicable on the last Jenkins LTS with security fixes in the > core. Strictly speaking, this is up to maintainers, but I

Re: Proposal for adopting the Jenkins trilead-ssh2 library

> On 08.04.2017, at 00:26, Stephen Connolly > wrote: > > Having said all that, if MC *wants* the fun of maintaining trilead, I'm fine > with that. I told him before he sent the email about the CloudBees plans, and he was fine with that. So unless someone

Re: How to remove public version information from Jenkins

> On 06.04.2017, at 11:12, Robert Sandell wrote: > > https://en.wikipedia.org/wiki/Security_through_obscurity Doing this can conceivably be part of a defense-in-depth strategy that tries to slow down potential attacker by making information gathering as difficult as

Removing unsafe old versions of plugins from update sites

Hi everyone, as discussed a while back[1], and implemented for the first time with Pipeline Classpath Plugin a few weeks ago[2], we started removing plugins with unfixed security vulnerabilities from distribution. What we haven't discussed is what to do with plugins that receive fixes: Should

Re: Confluence Source Editor

> On 04.04.2017, at 03:54, JordanGS wrote: > > Is there any plans on enabling the source editor in the future for the wiki, > see here. you should probably ask on the infra list. I'm not sure Tyler regularly reads the dev list. -- You received this message

Re: Fix for OS X postinstall script uid

> On 02.04.2017, at 11:04, amine choukir wrote: > > e. I tried to look for the postinstall in the git repo of jenkins but could > not find it. It's in https://github.com/jenkinsci/packaging (also the name of the Jira component to use) -- You received this message

Re: lost permission to write on jenkinsci/docker-ssh-slave

> On 30.03.2017, at 13:33, nicolas de loof wrote: > > not sure where to request this. Here is fine. Fixed. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving

Re: Plugin Pipeline Environment Variables

> On 27.03.2017, at 15:47, David Brooks wrote: > > However, I do not see any documentation around Step and BuildStep has been > deprecated. I just need a little nudge in the right direction, not the full > solution. I think

Re: Repository access nodejs-plugin

> On 27.03.2017, at 12:56, Nikolas Falco wrote: > > my user name for jenkins JIRA is nfalco, I will appreciate a lot your help > for default assignee of NodeJS component becuase since now I have to look up > every day for new issues Done. -- You received this message

Re: I'd like to adopt the logstash plugin

> On 23.03.2017, at 17:12, Jakub Bocheński wrote: > > I still have no write access there though. Should be resolved now. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop

Re: Commit rights to cobertura-plugin

> On 24.03.2017, at 22:18, Steve Christou wrote: > > Would anyone else object to me taking ownership of the cobertura plugin also? > I am currently the core maintainer of cobertura. If no one has any > objections, I will add myself and mbarrien to the list of

Re: [Jenkins-infra] Any known consumers of the 'scm' element in update-center.json?

> On 13.03.2017, at 02:14, Daniel Beck <m...@beckweb.net> wrote: > > I'm asking because I'd like to redefine it to point to a full browsable SCM > URL to support linking to the correct SCM URL on plugins.j.io and don't want > to break things that still rely on the c

Re: Maven Repository 404 Not found?? Cannot build project.

> On 19.03.2017, at 01:35, JordanGS wrote: > > no longer found I would be surprised if it ever existed, as our artifacts are hosted on repo.jenkins-ci.org. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: Check credentials fails with ERROR

> On 17.03.2017, at 20:05, JordanGS wrote: > > Followed the hosting instructions found here. > > I wanted to verify that your credential is correctly recognized by Maven so i > ran mvn deploy > > Any advice would be appreciated. A quick Google search indicates

Re: What should we do with the CLI?

> On 15.03.2017, at 23:40, Jesse Glick wrote: > > Please read and comment (you can fork my gist if you just want to > suggest edits): > > https://gist.github.com/jglick/9721427da892a9b2f75dc5bc09f8e6b3 I'm very happy with this proposal. It's well thought out and

Re: Any known consumers of release-history.json?

> On 13.03.2017, at 04:52, Daniel Beck <m...@beckweb.net> wrote: > > This is about http://updates.jenkins-ci.org/release-history.json > > Are there any known consumers for that file except jenkins.io/release.rss > (which also drives @jenkins_release on Twitter)

Re: Rename of http_request artifactId

> On 17.03.2017, at 16:28, Janario Oliveira wrote: > > And It goes in other places. > > If there is a way to fix all this, I could keep the old name Jira link will be removed soon anyway since we currently have no great way to handle the naming inconsistencies

Re: Rename of http_request artifactId

> On 17.03.2017, at 15:54, Jesse Glick wrote: > > First of all, there is no mechanism in Jenkins to change the ID of a > plugin after people have installed it. So users will not see an > upgrade; they will just see an unrelated plugin. This. 4.5k users will be stuck on

Re: Naming convention for sprints in Jira

> On 15.03.2017, at 17:39, Kanstantsin Shautsou > wrote: > > Now it messed with statuses created for somebody needs. What are you referring to? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe

Re: Commit rights to matrix-auth-plugin

> On 15.03.2017, at 11:31, Christopher Orr wrote: > > I've asked the bot again just now, but it seems to be asleep. Maybe a > GitHub admin can take a look: > https://github.com/jenkinsci/matrix-auth-plugin > https://github.com/mathias-nyman Fixed. Probably one of the leftover

Re: How to call a groovy function from a Jenkinsfile?

> On 14.03.2017, at 23:27, Christopher Orr wrote: > > Such a question is very unwieldy, and makes it harder for people to > answer. Please reproduce the problem in a bare-minimum Pipeline and > update your question on SO. On top of all that, it's been posted to the wrong

Re: [Jenkins-infra] Heads Up: JIRA DVCS integration disabled on issues.jenkins-ci.org

> On 14.03.2017, at 22:08, Marcin Zajączkowski wrote: > > Have you guys tried to contact GitHub support and talk about that? http://lists.jenkins-ci.org/pipermail/jenkins-infra/2016-October/000893.html -- You received this message because you are subscribed to the Google Groups

Re: Commit rights to cobertura-plugin

Nice, well written request. Re Ulli's old email address no longer working, I'm adding him in CC. > On 13.03.2017, at 21:27, Michael Barrientos wrote: > > I would like to get commit rights to > http://github.com/jenkinsci/cobertura-plugin. > > Per instructions on both

Naming convention for sprints in Jira

Hi everyone, it seems sprints in Jira are globally visible (across projects), and, when editing an issue, provide little context as to what that sprint is. I think some sort of prefix in names should be adopted by everyone using sprints in Jira -- basically James D right now -- to make it easy

Re: Error when running maven command to release on jenkins-ci.org

> On 13.03.2017, at 15:15, JordanGS wrote: > > published half the files for some reason, so i believe that caused the hidden Right, you're not allowed to delete, which is what overwriting does (delete + create). That version number is burnt, use the next one. --

Re: Error when running maven command to release on jenkins-ci.org

> On 13.03.2017, at 11:10, Robert Sandell wrote: > > You might not be on the list of contributors allowed to upload artifacts > https://github.com/jenkins-infra/repository-permissions-updater He is, but may be using a different account now. -- You received this

Any known consumers of release-history.json?

Hi everyone, This is about http://updates.jenkins-ci.org/release-history.json Are there any known consumers for that file except jenkins.io/release.rss (which also drives @jenkins_release on Twitter)? Thanks! Daniel -- You received this message because you are subscribed to the Google

Re: [Jenkins-infra] Any known consumers of the 'scm' element in update-center.json?

> On 13.03.2017, at 02:14, Daniel Beck <m...@beckweb.net> wrote: > > It was introduced in > https://github.com/jenkins-infra/backend-update-center2/commit/e68790e1d48848a1b3db59b84ec3c6e9815bd351 > with no explanation of its purpose, so cc'ing Andrew. Oops, wrong link. I

Any known consumers of the 'scm' element in update-center.json?

Hi everyone, Are you aware of consumers of the 'scm' element in the update-center.json files that currently just points to a domain? It was introduced in https://github.com/jenkins-infra/backend-update-center2/commit/e68790e1d48848a1b3db59b84ec3c6e9815bd351 with no explanation of its purpose,

Re: [ANN] Change to how the update center JSON files are created

> On 10.03.2017, at 12:00, Fritz Elfert wrote: > > However: The link generator apparently needs some more work. > > Links on the left top ("GitHub", "Open Issues", "Latest rolling changes" > "Changes in x.x release") seem to be broken with some plugins: > > E.g. broken

Re: [ANN] Change to how the update center JSON files are created

> On 10.03.2017, at 08:53, Gavin Mogan wrote: > > Is the wiki going away No. We cut the wiki dependency to allow the wiki to be updated etc. without worrying about breaking the update center, not to get rid of it.

Re: [ANN] Change to how the update center JSON files are created

> On 10.03.2017, at 00:18, Raphael Pionke wrote: > > BTW: Can we adjust the links from https://twitter.com/jenkins_release to use > the new plugins.jenkins.io page? Right, that would be nice. https://github.com/jenkins-infra/backend-update-center2/pull/118

Re: Shoudn't search in Jenkins be case-insensitive by default?

> On 08.03.2017, at 11:37, Marcin Zajączkowski wrote: > > I don't know if there were any strong arguments to have searching > case-sensitive by default a few years ago or it was just set to that mode. > Therefore, I would ask what do you think about that and about a possibility

Re: Alternative to a BuildWrapper extension point

> On 08.03.2017, at 03:16, Lucas Machado wrote: > > Now my BuildWrapper is subject to this 5min timeout and it gets an > InterruptedException on case it takes longer to run > I have a special use case that it can takes a little more the this 5 minutes > to run. > My

Re: [ANN] Change to how the update center JSON files are created

> On 07.03.2017, at 23:12, Daniel Beck <m...@beckweb.net> wrote: > > Since we now cannot rely on the wiki pages to exist, how can be accomplish > the goals of having some minimal information for all plugins? Well, since > October or so, we have plugins.jenkins.io, with a

[ANN] Change to how the update center JSON files are created

Hi everyone, I pushed a change to the update center today. TLDR: Wiki edits could have inadvertently removed plugins from the update site, breaking the suggested plugin installation experience for new Jenkins users. We fixed that by no longer relying on wiki data during update site generation.

Re: Proposal to support only the latest version of Safari

> On 07.03.2017, at 21:03, is@ wrote: > > After looking at the Jenkins Browser Compatibility Matrix I have noticed that > Safari has level 1 support for versions 6 and newer. Since Safari is an > evergreen browser, I would like to propose to support only the latest

Re: Jenkins + Gradle + Android testing (Espresso) = Get builds to show 'failed'

> On 07.03.2017, at 15:41, Lucy StandUp wrote: > > Currently using the latest version of Jenkins Pipelines. > > Having difficulty with Gradle + Jenkins Pipelines + Espresso (Android) tests. > > Would like to have Jenkins’ builds show failed if tests failed. > > Any

Re: HEADS UP: Planning to de-provision l10n.jenkins.io

> On 02.03.2017, at 06:10, R. Tyler Croy wrote: > > This literally affects nobody Do you know how many translations we receive via the translation assistance plugin? We probably should also rebrand that plugin, rather that deprecate/tombstone it, as it allows

Re: No infobox information displayed on plugin wiki page

> On 01.03.2017, at 18:06, mohan kumar wrote: > > I guess it will get the infobox information in some time. Thanks again. Add a query parameter, e.g. ?nocache, to bypass caching. See my link in the previous email. -- You received this message because you are

Re: need of a https://github.com/jenkins-infra/repository-permissions-updater , plugin git repository assist

> On 01.03.2017, at 17:00, Gabe Montero wrote: > > So I'm listed as a developer for the openshift-sync plugin here: > https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-openshift-sync.yml#L7 > > However if you look at the

Re: No infobox information displayed on plugin wiki page

> On 01.03.2017, at 16:00, mohan kumar wrote: > > The plugin that I maintain is missing its infobox on the wiki page. It was > always properly showed but is not shown anymore. Is anyone be able to show me > the way to solve this? > >

Re: The future of the patron program

> On 27.02.2017, at 23:56, Oleg Nenashev wrote: > > it would be great if the Jenkins Board shares info a kind of the Jenkins > budget stats for previous years. It is hard to estimate how much the program > contributes compared to other sources (I'd guess it contributes

Re: Rename Plugin Title

> On 28.02.2017, at 01:51, Gavin Mogan wrote: > > Since Jenkins removes the start of Jenkins, is there any restriction on the > use of the name? I saw cloudbees before has had to apply for use, but I know > thats for seperate projects. > > We want to rename it to "Sauce

Re: Jenkins email Notifications with pipeline view in email body.

> On 27.02.2017, at 19:19, Siva varma Datla wrote: > > Is there anyway to do that? Please ask questions like this on the jenkinsci-users mailing list: https://jenkins.io/mailing-lists/ -- You received this message because you are subscribed to the Google Groups

Re: Rename Plugin Title

> On 27.02.2017, at 09:14, Gavin Mogan wrote: > > Is it as simple as renaming the wiki page, and updating the in the > pom.xml file? I vaguely remember something about items in the update center > not showing up if the wiki page didn't match the plugin page but I can't

The future of the patron program

Hi everyone, This is about the patron program: https://wiki.jenkins-ci.org/display/JENKINS/Patron+of+Jenkins+program While we have never 'reviewed' the program as described on the wiki page, the project meeting has continued to approve donor messages whenever there were changes, and patrons

Re: Accessing credentials store from the Jenkins CLI before unlocking Jenkins

> On 21.02.2017, at 18:02, 'Claudiu Guiman' via Jenkins Developers > wrote: > > But I can’t list credentials. Is it because the temporary admin account > doesn’t have the right permissions? Please use the jenkinsci-users mailing lists for questions like this.

Re: Post-build-email directs to all-changes page instead of detailed build ID page (v2.45)

> On 10.02.2017, at 11:16, Enoch wrote: > > we noticed that post-build mails suffixes "?page=changes" to the detail URL > recently. > Does somebody feel responsible or knows how to change such behavior? > Hi, Please use our bug tracker to report bugs. In this case,

Re: Requesting Java 8 builds for selenium plugin

> On 21.02.2017, at 13:12, rouke.broer...@infosupport.com wrote: > > Is there any documentation on the change to ci.jenkins.io? The only thing I > can find right now is this thread: > https://groups.google.com/forum/#!topic/jenkinsci-dev/439-IDYNSVY about a > trial on using ci.jenkins.io to

Re: Build details of pipeline job via API

> On 20.02.2017, at 18:19, Graham Lyons wrote: > > I'm trying to get information about running builds on Jenkins agents, with > and without pipelines. Please ask questions like this on the jenkinsci-users mailing list. https://jenkins.io/content/mailing-lists Thanks!

Re: Jelly/Plugin pipeline script support for optionalBlock

> On 20.02.2017, at 12:31, Robert Sandell wrote: > > https://wiki.jenkins-ci.org/display/JENKINS/Marking+a+new+plugin+version+as+incompatible+with+older+versions … which should be only used when there's really no way to make work.

Re: Changelog is now YAML and lives in the site repository

> On 20.02.2017, at 11:37, Arnaud Héritier wrote: > > I don't like to have the changelog leaving outside of the project repository. It already was in the case of LTS (which AFAIK is the line more successful with users since we made it more discoverable on the site), and

Changelog is now YAML and lives in the site repository

Hi everyone, I moved the changelog to the site: https://github.com/jenkins-infra/jenkins.io/blob/master/content/_data/changelogs/weekly.yml All that's left in jenkinsci/jenkins is a tombstone file directing people to the file above:

Re: plugin data migration - potential incompatibility

> On 17.02.2017, at 21:38, Jesse Glick wrote: > > In that case maybe just rename the `Builder` class rather than even > wasting time on migration. + https://wiki.jenkins-ci.org/display/JENKINS/Marking+a+new+plugin+version+as+incompatible+with+older+versions -- You

Re: How to terminate Jenkins build in Pipeline Global Library code

> On 17.02.2017, at 21:20, Peter Zhao wrote: > > Hi Jenkins gurus, Please ask questions like this on the jenkinsci-users mailing list. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this

Re: Discontinuing Office Hours

> On 15.02.2017, at 18:21, Daniel Beck <m...@beckweb.net> wrote: > > Anyone opposed? If not, I'll implement this. I removed it from the event calendar, and updated the wiki page. If I see more references, I'll clean those up as well. -- You received this message because you

Re: Update Center not updating?

> On 16.02.2017, at 23:29, Shawn MacArthur wrote: > > I've updated a plugin here > > https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/nouvola-divecloud/ > > but the latest version doesn't appear in > > https://updates.jenkins-ci.org/update-center.json >

Re: Email-ext plugin conflicting with token-macro plugin

> On 16.02.2017, at 20:56, Pino Alu wrote: > > Using Jenkins core v 1.625.3 Jenkins 2.16 and up tell you when your plugin configuration is invalid and refuse to load plugins with unsatisfied dependencies. I recommend you upgrade to a recent release. Also, please ask

Re: plugin data migration - potential incompatibility

> On 16.02.2017, at 07:47, Robert St. John wrote: > > Does Jenkins offer a mechanism to support a data migration like this? These are the resources we currently have for format changes: - http://javadoc.jenkins-ci.org/index.html?hudson/XmlFile.html -

Discontinuing Office Hours

Hi everyone, Remember Office Hours? Yeah, me neither. https://wiki.jenkins-ci.org/display/JENKINS/Office+Hours Lately we've done Office Hour-style presentations much more successfully via the Jenkins Online Meetup. I propose we remove office hours from our calendar, update wiki pages to

Re: Evaluation of a Prototype Identifying Unnecessary Code

> On 13.02.2017, at 13:11, 'Roman Haas' via Jenkins Developers > wrote: > > In the attachment, you find a file that lists ten suggestions for unnecessary > code in your code base. Each suggestion consists of one or more files or > packages; if there are

Re: Failing when accessing to repo.jenkins-ci.org

> On 13.02.2017, at 13:04, Sean Flanigan wrote: > > I'm having the issue too. Would you please let us know the result? Got a canned response so far, nothing else. Will respond to http://lists.jenkins-ci.org/pipermail/jenkins-infra/2017-February/001033.html once I

Re: PLUGIN: mvn deploy doesn't seem to work with my credentials

> On 10.02.2017, at 19:05, Victor Martinez > wrote: > > from the maven configuration is failing, so I don't know how to debug > further, any ideas/hints? Make this ID match the one in settings.xml so Maven knows this is the same repo:

Re: Failing when accessing to repo.jenkins-ci.org

Already asked JFrog for help (my message seems stuck in the moderation queue of the infra list), no response so far. > On 09.02.2017, at 23:32, Victor Martinez > wrote: > > Can you login to https://repo.jenkins-ci.org/webapp/#/login ? I tried to > reset my

Re: Windows builds/tests for core disabled

> On 08.02.2017, at 21:58, Slide wrote: > > It doesn't look like it did, I only see a Linux build happening see [1]. I > don't think I have direct commit rights on jenkinsci/jenkins. I created a branch and added the Windows build back on it.

Re: Jenkins parameters weather to send an email notification or not

> On 08.02.2017, at 21:57, siva.datla...@gmail.com wrote: > > th process to follow please You could start by asking this on the correct mailing list. https://jenkins.io/content/mailing-lists -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: Windows builds/tests for core disabled

> On 06.02.2017, at 18:23, Slide wrote: > > Just skipping them seems too hacky to me. IMO we should get Windows testing back ASAP -- so if skip on Windows + TODO comment gets us there more quickly, we should do so. While it doesn't improve the Windows coverage, it will

Re: Jenkins Migration plan | 1.585 -> LTS 2.32.1

This is not a dev list question. Also, don't cross-post. > On 06.02.2017, at 07:20, Vikrant Kaushik wrote: > > Dear All, > > This weekend I'm planning to upgrade my Jenkins as per below Migration plan: > > 1.585 -> LTS 2.32.1 > > Request all of you to please

Re: TestPluginManager error during tests

> On 02.02.2017, at 20:35, Slide wrote: > > I have verified that the message does exist, so I'm kind of at a loss. Did the localizer run? I.e. are there generated sources for Messages.java? -- You received this message because you are subscribed to the Google Groups

Re: User not passing to job history if submitted by URL?

> On 02.02.2017, at 19:51, Don Alcombright wrote: > > Any thoughts on what I am doing wrong? This is not a question for the developers list. Please ask questions like this on the users list. -- You received this message because you are subscribed to the Google

Re: Update Swarm plugins' remoting dependency

> On 01.02.2017, at 20:09, ta...@appscode.com wrote: > > Now that I got you here Uh… https://github.com/jenkinsci/swarm-plugin/commits/master?author=jglick Whatever your request is, Jesse is probably the wrong person to ask. -- You received this message because you are subscribed to the

Re: New instance types in ec2-plugin

> On 01.02.2017, at 15:10, Ihor Bilovus wrote: > > Please add new instance types (i.e. m4.16xlarge / r4.16xlarge and so on) to > ec2-plugin. This is not where, or even how, you ask for changes. -- You received this message because you are subscribed to the Google

Re: Creating and managing parameterized build from Plugin

> On 01.02.2017, at 11:28, Harsh Agarwal wrote: > > 2. While building with parameters the project, the values of the variables > should be pre-computed and provide a dropdown to the users to choose from. We're at around half a dozen plugins that do something like

Re: Deploying a file on a remote location

> On 01.02.2017, at 12:37, gaurav lele wrote: > > using the ArtifactDeployer plugin Please ask questions like this on the jenkinsci-users mailing list. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: How to get workspace of jenkins pipeline job (WorkflowRun java API )

> On 30.01.2017, at 16:41, Ayellet wrote: > > (in other words: I need an access from my plugin (java plugin), during > hudson.model.listeners.RunListener flow. A Pipeline run/build can have any number of different workspaces on different nodes in parallel, so the notion

Re: Opening up snapshot deployment

> On 28.01.2017, at 21:16, Mark Waite wrote: > > Log is appended to the end of the message. > > I'm building from https://github.com/MarkEWaite/git-plugin using branch > master-PR463-add-git-lfs. It includes a dependency on git-client-plugin > 2.3.0-SNAPSHOT which

Re: Opening up snapshot deployment

> On 28.01.2017, at 19:56, Mark Waite wrote: > > when I try to download them from the web UI (or from my git plugin build), > they fail to download. I get that the UI fails, as the reverse proxy config is broken (see the extra 'jenkinsci' as web app context on

Re: Crawler Pull Request approved but not yet merged

> On 27.01.2017, at 21:57, Keith Collison wrote: > > not yet merged. Done. -- 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

Re: How to remove "plugin is up for adoption" warning message from wiki plugin page

> On 27.01.2017, at 09:51, 'Nikolas Falco' via Jenkins Developers > wrote: > > I already release two new versions but the Wiki page of Plugin continue to > show warning message: "This plugin is up for adoption. Want to help improve > this plugin?" Clicking

Re: How can I distinguish between two custom steps of the same class?

> On 26.01.2017, at 19:52, Moshe Cohen wrote: > > Can you point me to an example that does what you just mentioned? > This PR (that I really need to finish some time…) does something similar in Copy Artifact: https://github.com/jenkinsci/copyartifact-plugin/pull/32 A

Re: How to get JSON output of POSTMAN/NEWMAN in Jenkins HTML Report generator

This is the Jenkins developers mailing list. Please ask on the Jenkins users mailing list instead. -- 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

Re: Bug Triage "Team"

> On 21.01.2017, at 15:07, Baptiste Mathus wrote: > > adding the NEW status > > Having a state to basically say: "this is issue is new, but has not been > reviewed, so may be invalid/incomplete/whatever for whatever reason" makes > sense IMO. Shouldn't we create a new "To

Re: How can I establish communication with a GitHub repository to exectute .robot files I have in github?

This is not an appropriate question for this list. -- 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. To view

Re: Not able to release new version of plugin

> On 15.01.2017, at 19:08, Irfan Sayed wrote: > > I have just removed the ID in the distributionManagement from POM WHY? WHY remove it altogether after being told to change it to the same value as something else? I give up. -- You received this message because you are

Re: Not able to release new version of plugin

> On 15.01.2017, at 19:08, Irfan Sayed wrote: > > still same unauthorized issue > What's the effective POM now? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving

Re: Not able to release new version of plugin

> On 15.01.2017, at 18:34, Irfan Sayed wrote: > > Can you please quickly review and see any issue. > Change the IDs of distributionManagement as well. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: Not able to release new version of plugin

> On 15.01.2017, at 17:52, Irfan Sayed wrote: > > so what would be the correct ID ? > java.net-m2-repository OR repo.jenkins-ci.org ?? > Doesn't matter, just needs to match. FWIW recent parent POMs used maven.jenkins-ci.org, so you may be able to just remove that

Re: Not able to release new version of plugin

The password is defined for the repo ID: java.net-m2-repository The upload goes to the repo ID: repo.jenkins-ci.org Am I missing something here? Isn't this the problem? > On 15.01.2017, at 10:05, Irfan Sayed wrote: > > http://maven.apache.org/SETTINGS/1.1.0;> > >

Re: Not able to release new version of plugin

> On 14.01.2017, at 18:39, Christopher Orr wrote: > > Since last month, no special permissions are needed to upload SNAPSHOTs: > https://groups.google.com/d/msgid/jenkinsci-dev/53CC6ED4-3BBC-4FAD-A197-10AD7F922A34%40beckweb.net > > The permissions look correct here, and match

Re: Maintainer request for the Gatling plugin

> On 13.01.2017, at 13:42, Baptiste Mathus wrote: > > Yes and no. There are definitely some similarities, sure, but this is case is > not an adoption IIUC? We should update https://wiki.jenkins-ci.org/display/JENKINS/Pull+Request+to+Repositories -- This unfortunately named

Re: Not able to release new version of plugin

> On 11.01.2017, at 17:34, Irfan Sayed wrote: > > not getting why "unauthorized" error is coming Have you looked into all of the suggestions in the 12th note at https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues ? --

Re: Dealing with vulnerable plugins

> On 02.11.2016, at 13:59, Daniel Beck <m...@beckweb.net> wrote: > > 3. Add metadata to the plugin site indicating vulnerable plugins to inform > admins who already have the plugin installed. FTR this feature made it into 2.40 and Oliver accepted it into 2.32.2. Some scree

Re: confused by new Jenkins plugins web pages

> On 07.01.2017, at 01:47, Moshe Cohen wrote: > > 1) Where is the link to the Github repo? I filed this https://issues.jenkins-ci.org/browse/WEBSITE-279 > 2) How can I edit the page itself when there is an update? The documentation content is still sourced from the plugin

Re: ConfigurationSlicing plugin looking for new ownership

> On 06.01.2017, at 16:16, Michael Donohue wrote: > > I would love for someone to take on this plugin. I tagged its wiki page to increase the visibility of this. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: Not able to release new version of plugin

> On 06.01.2017, at 14:26, Irfan Sayed wrote: > > 2.3 > The first response you got linked to: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues And it says: > … or update to the parent plugins POM 2.5 or newer

<    4   5   6   7   8   9   10   11   12   13   >