Re: Proposal: Emeritus maintainers

On Monday, 2 March 2020 12:56:10 UTC, Daniel Beck wrote: > > > > On Mon, Mar 2, 2020 at 1:50 PM Stephen Connolly > wrote: > >> >> Similarly, if I come back in 2 years and see that Bob who adopted the >> foobar plugin from me has done nothing with it i

Re: Proposal: Emeritus maintainers

On Monday, 2 March 2020 12:47:35 UTC, Stephen Connolly wrote: > > > > On Monday, 2 March 2020 12:44:37 UTC, Baptiste Mathus wrote: >> >> >> >> Le lun. 2 mars 2020 à 13:40, Stephen Connolly a >> écrit : >> >>> >&g

Re: Proposal: Emeritus maintainers

On Monday, 2 March 2020 12:44:37 UTC, Baptiste Mathus wrote: > > > > Le lun. 2 mars 2020 à 13:40, Stephen Connolly > a écrit : > >> >> >> On Monday, 2 March 2020 11:19:07 UTC, Daniel Beck wrote: >>> >>> >>> >>> On Mo

Re: Proposal: Emeritus maintainers

On Monday, 2 March 2020 11:19:07 UTC, Daniel Beck wrote: > > > > On Mon, Mar 2, 2020 at 12:02 PM Stephen Connolly > wrote: > >> If all maintainers of a plugin are emeritus and someone wants to claim >> ownership then the emeritus maintainers can short-circuit

Re: Proposal: Emeritus maintainers

y mark plugins for adoption. Now it > can be done by just setting a GitHub topic: > https://jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/ > > BR, Oleg > > On Monday, March 2, 2020 at 12:06:21 PM UTC+1, Marky Jackson wrote: >> >> I like this idea so a +1 from me

Proposal: Emeritus maintainers

Can we add a concept of emeritus maintainer... by just commenting out their username in the corresponding repository-permissions-updater yaml file? An emeritus maintainer would be indicating that they are no longer active, but if they want to re-activate they do not need to wait for existing

Re: Replace authorize-project-plugin

On Tuesday, 27 August 2019 09:16:40 UTC+1, ikedam wrote: > > Hi, > > I’m Ikedam, a maintainer of authorize-project-plugin. > https://plugins.jenkins.io/authorize-project > > Authorize-project-plugin doesn’t support features of modern Jenkins, such > as pipelines, multibranch and JCaC. >

Re: Looking to help maintain credentials plugin

d this plugin falls into my > general category of security-related plugins that I've been working > with more frequently. > > -- > Matt Sicker > Senior Software Engineer, CloudBees > -- *Stephen Connolly* Principal Software Engineer CloudBees, Inc. [image: CloudBees-Logo

Re: Third party dependencies, APIs, and Jenkins: Proposals

On Wed 10 Apr 2019 at 21:55, Jesse Glick wrote: > On Wed, Apr 10, 2019 at 10:48 AM Matt Sicker > wrote: > > 1. Shade in third party dependencies of Jenkins core into Jenkins with > > a package rename. This will allow core to use the dependencies, but > > plugins will still need to include the

Re: Proposal: AWS Secrets Manager Credentials Provider plugin

unity for the stuff I believe to be important (credentials and scm-api). I am glad you have found (and are still finding) utility in the content. Feel free to create PRs with any suggested improvements as I am paying attention... just not as frequently ;-) - Stephen > > Chris > >

Re: Proposal: AWS Secrets Manager Credentials Provider plugin

It would be great to get any feedback on the docs I left for writing such things: https://github.com/jenkinsci/credentials-plugin/blob/master/docs/implementation.adoc#implementing-a-new-credentialsprovider On Thu 4 Apr 2019 at 17:10, Chris Kilding wrote: > Hi, > > That sounds good - we’re happy

Re: Why did Multiple SCMs Plugin get deprecated?

ResolveSCM is for the use case where you want to checkout a matching branch name in another repo... but fallback to other branches of it doesn’t exist. Eg Apache Maven uses it so that you can add a feature to Core (main git repo) and add integration tests (side git repo) and test them both in the

Re: openid plugin up for adoption

; Cheers! > > Le lun. 21 janv. 2019 à 12:38, Stephen Connolly < > stephen.alan.conno...@gmail.com> a écrit : > >> I don't know how me cutting a maintenance release resulting from a >> support ticket for a CloudBees customer many years ago has translated into >> the

openid plugin up for adoption

I don't know how me cutting a maintenance release resulting from a support ticket for a CloudBees customer many years ago has translated into the illusion that I am maintaining this plugin. It is open for adoption. I am not currently paying sufficient attention to the Jenkins community processes

Re: Using Jenkins JIRA to record development priorities for a plugin?

On Sun 9 Dec 2018 at 15:35, Mark Waite wrote: > > > On Sun, Dec 9, 2018 at 8:18 AM Daniel Beck wrote: > >> >> >> > On 9. Dec 2018, at 15:34, Mark Waite wrote: >> > >> > Is it allowed to use issues.jenkins-ci.org for that type of tracking? >> > >> >> I don't see why it would not be, or do you

Re: Detect Matrix Project

In the config pages, there will not be a ‘build’ context variable. What you want is to either check ‘it.descriptor’ as being the matrix project descriptor or check ‘it’ as being the matrix project class. But don’t even go there, in your descriptor override ‘isApplicable’ to return false for

Re: Looking to be added as a maintainer for pam-auth-plugin

ups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/66d8deb8-1661-44c9-8efe-c2fdcfbe8cc0%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/66d8deb8-1661-44c9-8efe-c2fdcfbe8cc0%40googlegroups.com?utm_medium=email_source=

Re: Suggestion: versioning the schema for Configuration as Code

But I still think you should include the (let’s invent a different name to show the purpose) meta-schema version Most likely the meta-schema version will always be 1, but if you ever need to revise then you will thank Jesse and I for suggesting it. CaaC has a schema for generating the schema at

Re: Upcoming JEP for usage of Incrementals repository

To be clear, this is a joint response from myself and James On Wed 16 May 2018 at 12:14, James Nord wrote: > So the objection I have is that as it stands in JEP-305 the versions are > releases and these are expected to be garbage collected. > > Anyone also wanting to

Re: Suggestion: versioning the schema for Configuration as Code

On Fri 11 May 2018 at 17:32, Jesse Glick wrote: > On Fri, May 11, 2018 at 11:14 AM, nicolas de loof > wrote: > > we discover "jenkins" has a "securityRealm" attribute and some > > implementation can be used to set this attribute. This directly

Re: FYI: On naming SCM implementation and extension plugins

On Tue 17 Apr 2018 at 17:18, Jesse Glick wrote: > On Tue, Apr 17, 2018 at 11:10 AM, Carles Capdevila Tejada > wrote: > > should I change it before into gitblit-scm? > > According to the doc, since > > https://plugins.jenkins.io/gitblit > > does not

Re: Anything wrong with storing expanded plugin data in var cache?

I see nothing wrong with it... but I would say that having added the --pluginroot option myself iirc ;-) On 24 March 2018 at 00:29, Sam Gleske wrote: > I normally store expanded plugin metadata within > /var/cache/jenkins/plugins similar to how WAR filre metadata is

Re: Multibranch event listener for Github PR labels

On Mon 19 Mar 2018 at 08:39, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > On Mon 19 Mar 2018 at 08:13, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> >> On Mon 19 Mar 2018 at 00:50, Steven F <stevengfos...@gmail.com> wrote:

Re: Multibranch event listener for Github PR labels

On Mon 19 Mar 2018 at 08:13, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > > On Mon 19 Mar 2018 at 00:50, Steven F <stevengfos...@gmail.com> wrote: > >> I locally modified GHBS to make the constructors for PullRequestSCMHead >> and PullRequestSCMRe

Re: Multibranch event listener for Github PR labels

On Mon 19 Mar 2018 at 00:50, Steven F wrote: > I locally modified GHBS to make the constructors for PullRequestSCMHead > and PullRequestSCMRevision public which has seemingly solved the problem. > What did I do in Gitea plugin? If I made the constructor public there,

Re: plugin development: add global environment settings

On Sat 10 Mar 2018 at 15:04, Daniel Beck wrote: > > > On 9. Mar 2018, at 09:43, Johann wrote: > > > > guys nobody can help me? Should I show some more of my code Global.jelly is to configure the descriptor rather than the instance To use

Re: Trademark sublicense request: CloudBees Jenkins Metrics

it would be great to get feedback from the maintainer of the Metrics > Plugin <https://wiki.jenkins.io/display/JENKINS/Metrics+Plugin> (Stephen > Connolly?). > If CloudBees plans to release a "CloudBees Jenkins Metrics Plugin" as a > part of this new product, it m

Re: Evergreen packaging for Jenkins Essentials

Looks good to me. My only concern is mixing three VMs in the one container. Python, node and java... would be nicer if that could be reduced... but ack that it’s non-trivial to do so On Wed 7 Feb 2018 at 21:28, R. Tyler Croy wrote: > In the same vein as my previous email,

Eh why are we suggesting such a complex reverse proxy configuration?

https://twitter.com/connolly_s/status/961223121981399040 for example, here is a working haproxy configuration without any crazy rewrite rules: frontend jenkins mode http bind *:80 use_backend jenkins frontend jenkins-tls mode https bind *:443 crt /path/to/server.pem

[ANN] Basic Branch Build Strategies plugin

If you are using Multibranch, you may be interested in: https://github.com/jenkinsci/basic-branch-build-strategies-plugin Checkout the documentation: https://github.com/jenkinsci/basic-branch-build-strategies-plugin/blob/master/docs/user.adoc This extension plugin will enable things like: *

Re: Calling a DSL extension resulting in error

The "I have a created a DSL plugin" at the start of the mail is the hint I am looking at... now it may be a script approval issue, but that may actually instead point to a question as to how to annotate a newly developed extension to mark the script safe methods... or it may be plain script

Re: Calling a DSL extension resulting in error

On Wed 3 Jan 2018 at 08:24, Victor Martinez wrote: > Please ask to the jenkinsci-users mailing list: > https://jenkins.io/mailing-lists/ > The poster is *clearly* asking a question about plugin development. This is the correct list for that. The users list is

Re: slf4j & TaskListener.getLogger intercept

Running build related things in the Jenkins JVM is kind of an anti-pattern IMHO. Better to fork a JVM that you have complete control over the classloader, in which case the logging goes to STDOUT and you just pipe that to the build log On 18 December 2017 at 20:16, Shaun Thompson

Re: Adding config when plugin updates

What you might need to do is set a flag that signals at least one readResolve method has assigned an id (or better have a set of newly assigned ids). Then have a @Initializer that fires after Jobs loaded and it checks the flag (or set non-empty) and if set then it iterates all jobs saving ones

Re: GitHub MultiBranch building when I create a tag

On Sat 9 Dec 2017 at 23:14, Mark Waite wrote: > Stephen added tag discovery as a response to user requests. Building from > a tag is likely to require different specialized behaviors for different > users. > > Some users won't mind if a tag is built more than once.

Re: Removing the Everyone team in the jenkinsci GitHub org

On Fri 1 Dec 2017 at 15:49, Daniel Beck wrote: > > > On 29. Nov 2017, at 14:52, Daniel Beck wrote: > > > > Details TBD. I currently plan to make people collaborators with write > access. This will need to be cleaned up some time in the future, but >

Re: [PROPOSAL] Change core logging from Java Utils Logging

On Mon 27 Nov 2017 at 22:51, Jesse Glick <jgl...@cloudbees.com> wrote: > On Wed, Nov 22, 2017 at 2:07 PM, Stephen Connolly > <stephen.alan.conno...@gmail.com> wrote: > > there is the logging of incorrect values > > I guess this is a concern according to the ha

Re: SCM plugin not appearing as SCM option in project configuration

On Fri 24 Nov 2017 at 08:13, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > > On Fri 24 Nov 2017 at 00:40, José Lamas Ríos <j...@genexus.com> wrote: > >> Hi, >> >> Newbie here, newbie on Jenkins and even newbie on Java :) >

Re: SCM plugin not appearing as SCM option in project configuration

On Fri 24 Nov 2017 at 00:40, José Lamas Ríos wrote: > Hi, > > Newbie here, newbie on Jenkins and even newbie on Java :) > > I'm trying to write a new SCM plugin. > > // com.genexus.gxserver/GeneXusServerSCM.java > public class GeneXusServerSCM extends SCM implements

Re: [PROPOSAL] Change core logging from Java Utils Logging

On Wed 22 Nov 2017 at 17:26, Jesse Glick <jgl...@cloudbees.com> wrote: > On Mon, Nov 20, 2017 at 10:32 AM, Stephen Connolly > <stephen.alan.conno...@gmail.com> wrote: > > log(Level.FINE, ()-> "simple concat " + localVar) > > > > is worse when

Re: [PROPOSAL] Change core logging from Java Utils Logging

e Glick <jgl...@cloudbees.com> wrote: > On Fri, Nov 17, 2017 at 10:41 AM, Stephen Connolly > <stephen.alan.conno...@gmail.com> wrote: > > JMH says Indy is slower > > Sorry, what are “JMH” and “Indy”? > > Where is the evidence that there is any actual performance issu

Re: Propose a workaround of missing multiple security realm feature

On Mon 20 Nov 2017 at 14:10, Daniel Beck <m...@beckweb.net> wrote: > > > On 20. Nov 2017, at 10:24, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > > > > In group membership is going to be tricky (not impossible) as you will > need to know w

Re: Propose a workaround of missing multiple security realm feature

On 18 November 2017 at 14:57, wrote: > Jenkins currently does not support multiple security realm. > However, it should be a reasonable use case that allow both AD / LDAP > logins for individuals (e.g. developers) and logins local Jenkins' own user > database for

Re: [PROPOSAL] Change core logging from Java Utils Logging

On Fri 17 Nov 2017 at 15:34, Jesse Glick wrote: > On Fri, Nov 17, 2017 at 8:47 AM, James Nord wrote: > > I just found myself having to write a > > LogRecord to log a paramaterized log with an exception... > > LOGGER.log(Level.FINE, ex, () -> "so why

[ANN] Credentials Plugin 2.2.0 to require Jenkins 2.60.1+

>From http://stats.jenkins.io/pluginversions/credentials.html 28% of people have upgraded credentials to 2.1.16 91% of installations of credentials 2.1.16 are using Jenkins 2.60.1 or newer It is 2 months since the 2.1.16 release of the credentials plugin. The 72% of people who have not upgraded

Re: Request for feedback: Jenkins Enhancement Proposal (JEP)

animal sniffer could be adapted to assist, for example On 31 October 2017 at 16:32, Jesse Glick wrote: > On Tue, Oct 31, 2017 at 11:43 AM, Robert Sandell > wrote: > > Not having to > > also browse through potentially thousands of lines of code in

Re: My video tutorial series on plugin dev for Jenkins at Apache

o implement SCM Source for Accurev? > :P > I'll definitely keep a eye out for these videos <3 > > Once work allows me to focus on Accurev Plugin, sure. > > > Den mandag den 30. oktober 2017 kl. 19.56.36 UTC+1 skrev Stephen Connolly: >> >> I’ve been recording a series of

Re: My video tutorial series on plugin dev for Jenkins at Apache

Oh and these are all live, unscripted and unedited. Stuff goes wrong and stuff even goes unexpectedly right (episode 3) but I believe that’s more interesting as it shows how to solve issues with developing in Jenkins On Mon 30 Oct 2017 at 18:56, Stephen Connolly < stephen.alan.conno...@gmail.

My video tutorial series on plugin dev for Jenkins at Apache

I’ve been recording a series of (approx 20min) videos focused on getting better usage of Jenkins at Apache. The first episode is live. https://youtu.be/W8BRtJmq_2Y The second is a “double episode” as I wanted to get to an MVP. If you are interested in plugin development you might like the

Re: Dynamically populate drop down in builder interface

On Sun 29 Oct 2017 at 06:43, 'Marco Brondani' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Hello, > I have a plug-in that uses Jenkins credentials to store API key and > details necessary to make requests when the plug in runs. > However, to improve the Builder interface, I'd

Re: Jenkins.createProject - ACL

On 24 October 2017 at 19:11, Jesse Glick wrote: > On Tue, Oct 24, 2017 at 1:23 PM, Shaun Thompson wrote: > > By logged in user, I'm referring to the user that initiated the plugin > > installation. > > There is no information available to that effect, if

Re: freestyle-multibranch, multibranch, scm-api questions

On 20 October 2017 at 21:14, Kanstantsin Shautsou <kanstantsin@gmail.com > wrote: > > > On Friday, October 20, 2017 at 2:16:41 PM UTC+3, Stephen Connolly wrote: >> >> >> >> On 20 October 2017 at 04:02, Kanstantsin Shautsou <kanstan...@gmail.com>

Re: freestyle-multibranch, multibranch, scm-api questions

On 20 October 2017 at 04:02, Kanstantsin Shautsou <kanstantsin@gmail.com > wrote: > > > 2017-10-20 11:50 GMT+03:00 Stephen Connolly <stephen.alan.connolly@gmail. > com>: > >> On 19 October 2017 at 17:42, Kanstantsin Shautsou < >> kanstantsin..

Re: freestyle-multibranch, multibranch, scm-api questions

On 19 October 2017 at 17:42, Kanstantsin Shautsou wrote: > Trying to make multibranch support with not messed buildhistory by reusing > my flexible github triggering code and experience. > Unclear what you mean by "not messed build history"... with multibranch, each

FYI: On naming SCM implementation and extension plugins

I have published my recommendations on naming SCM API implementation and extension plugins: https://github.com/jenkinsci/scm-api-plugin/blob/master/docs/implementation.adoc#naming-your-plugin Also my guidance on where functionality should land:

Re: Warning during multi-branch Indexing

Nope Nope Nope... it's https://github.com/jenkinsci/pipeline-milestone-step-plugin/commit/7ecb946d1c54ed15a8f4bb9848cfaa9da7c6086f#diff-1918a0bfc343fead0364ffbc8e42b847 you just need pipeline-milestone-step 1.3.1 or newer On 4 October 2017 at 03:26, Stephen Connolly < stephen.alan.co

Re: Warning during multi-branch Indexing

I think that is an issue in cloudbees-folders plugin On 4 October 2017 at 03:02, pallen wrote: > Hi Guys, > > The p4-plugin shows a warning during multi-branch indexing when an old > branch is being removed: > > > Oct 04, 2017 10:19:46 AM hudson.model.listeners.ItemListener

Re: Speeding up the ATH

On Thu 28 Sep 2017 at 20:33, Jesse Glick <jgl...@cloudbees.com> wrote: > On Thu, Sep 28, 2017 at 2:51 PM, Stephen Connolly > <stephen.alan.conno...@gmail.com> wrote: > > writing good acceptance tests is a high skill and not something that > > can be easily crowdsour

Re: Speeding up the ATH

On Thu 28 Sep 2017 at 19:11, Mark Waite wrote: > On Thu, Sep 28, 2017 at 11:43 AM Jesse Glick wrote: > >> On Thu, Sep 28, 2017 at 10:42 AM, Mark Waite >> wrote: >> > Do we have any way of associating historical

Please retweet and vote

https://twitter.com/asfmavenproject/status/906451059966693376 -- Sent from my phone -- 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: [Announce] Gerrit CI workflow to become a brand-new Jenkins plugin

I recommend using the gitea plugin as a "clean" example of a branch source, as it is relatively feature complete (gaps are api gaps in gitea itself) and free of the rate limit and class migration noise in github and Bitbucket branch source plugins On Thu 7 Sep 2017 at 23:00, Luca Milanesio

Re: How to stop the current pipeline step?

; On lun. 4 sept. 2017 à 20:29 Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> On Mon 4 Sep 2017 at 17:47, Ivo Bellin Salarin < >> ivo.bellinsala...@gmail.com> wrote: >> >>> Hi all, >>> >>> I am implementing the pipel

Re: How to stop the current pipeline step?

On Mon 4 Sep 2017 at 17:47, Ivo Bellin Salarin wrote: > Hi all, > > I am implementing the pipeline functionality for an existing plugin. > Currently, on an eventual error the plugin sets the build status to > FAILURE: the build continues executing all the build steps

Re: New SCMSource trait: filtering old git references

re" plugins that enable the feature. > > El miércoles, 30 de agosto de 2017, 13:10:00 (UTC+2), Stephen Connolly > escribió: >> >> On 30 August 2017 at 01:03, Javier Delgado <witoko...@gmail.com> wrote: >> >>> Following this comment >>> <https://

Re: New SCMSource trait: filtering old git references

On 30 August 2017 at 01:03, Javier Delgado wrote: > Following this comment > , I was planning > on creating a new scm trait for excluding references according to a date > threshold. > > The idea after the trait would

Re: Sortable tables with non existing value but different attributes

Isn't it just a question of using the attribute to have sorting on that attribute? On 1 August 2017 at 01:52, Victor Martinez wrote: > Hi there, > > Any ideas how I can use the sortable type in a non value cell? I though I > could use the "data-sort" attribute in

Re: Proposal - Disabling JNLP1/2 and CLI1 protocols by default in new Installations

+1 On Fri 28 Jul 2017 at 08:53, Oleg Nenashev wrote: > Hi all, > > It is almost one year since the release of JNLP4 protocol in Remoting 3.0. > This protocol is available in Jenkins LTS since 2.32.1, and so far it > demonstrates good stability being compared to JNLP2 and

[ANN] Credentials plugin documentation

I have finally finished documenting the credentials plugin. You can find the documentation at https://github.com/jenkinsci/credentials-plugin/tree/master/docs I have also uploaded PDF versions of the documentation to the plugin's wiki page:

Re: Request to join the Jenkins Security Team

More the merrier IMHO, I am +1 on you joining On 24 July 2017 at 06:04, 'Bruno P. Kinoshita' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Hi Oleg, > > I had seen the security advisory, and in the Wiki and GitHub I can see > some progress made to fix some of the 5 issues. > >

Re: Help with blocking job execution per node

May need to extend core to support advertising it. If it's more than 100ms it is likely a new round On Fri 21 Jul 2017 at 19:56, Martin Weber <fifteenknots...@gmail.com> wrote: > Am Donnerstag, 20. Juli 2017, 21:01:13 CEST schrieb Stephen Connolly: > > On Thu 20 Jul 2017 at 19:1

Re: Help with blocking job execution per node

On Thu 20 Jul 2017 at 19:13, Martin Weber wrote: > Hi list, > > my plugins adds a build wrapper that starts and stop a daemon (similar to > xvfb > [1] plugin). > Only one daemon instance can be run at a time on a single node, so I want > to > block job execution

Re: Plugin/core version installation statistics

2.7 or 1.651 On 19 July 2017 at 10:02, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > Nice! > > > On Wed 19 Jul 2017 at 16:52, Daniel Beck <m...@beckweb.net> wrote: > >> Hi everyone, >> >> A question that comes up regularly: "What

Re: Plugin/core version installation statistics

Nice! On Wed 19 Jul 2017 at 16:52, Daniel Beck wrote: > Hi everyone, > > A question that comes up regularly: "What version of core should I depend > on in a plugin?". Maybe you don't want to arbitrarily limit who can use > your plugin, but want newer core features? This

Re: Create a user with ADMINISTER and without RUN_SCRIPTS permission (ATH test case)

you need to turn on the separation of permissions... system property or something like that On 13 July 2017 at 03:55, Ullrich Hafner wrote: > How can I configure a user in an ATH test case who can edit the Jenkins > global configuration (i.e., has ADMINISTER

Re: GitHub and Bitbucket branch source UI refactoring

the security fixes will just have to manually download the plugin updates. I was limited in what I could publicly say about the release plan until the security advisory was published today On 10 July 2017 at 06:46, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > Current thinking

Re: GitHub and Bitbucket branch source UI refactoring

Current thinking is the GA release will be Wednesday On 10 July 2017 at 06:36, Joseph P <joseph...@gmail.com> wrote: > ETA on Release? > > Den mandag den 26. juni 2017 kl. 18.13.07 UTC+2 skrev Stephen Connolly: >> >> On 26 June 2017 at 08:14, Joseph P <jose...@gm

Re: [Proposal] Making all things Stapler more declarative

, specific comments on specific details of the code in the PR) On 7 July 2017 at 03:06, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > Yes I was thinking that a custom javadoc handler would be useful. > Especially as there are inheritance of facets and fragments th

Re: [Proposal] Making all things Stapler more declarative

lerFragment("main") there > should be a corresponding > > @facet login the login page. > @fragment main add this to change the main part of the configuration page. > > in the javadoc of the class? > > /B > > 2017-07-06 13:16 GMT+02:00 Stephen Connolly <stephen.alan.con

ATTN: Plugin developers who use IntelliJ

Please vote for https://youtrack.jetbrains.com/issue/IDEA-175538 if you want to be able to plugin run unit tests from IntelliJ using recent versions of the plugin parent. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from

Re: [Proposal] Making all things Stapler more declarative

t opted into @StaplerObject yet That, to me, does not make for a compelling developer experience. WDYT? I am inclined to reject your method based idea and stick with class level annotations... there are only 11 classes in all of Jenkins core with more than 5 facets / fragments >

Re: github-branch-source 2.0.7 hpi missing

https://issues.jenkins-ci.org/browse/INFRA-1266 filed On 6 July 2017 at 02:39, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > Baptiste reports that https://updates.jenkins.io/download/plugins/gitlab- > plugin/ is also missing... something is going on very strange > &

Re: github-branch-source 2.0.7 hpi missing

Baptiste reports that https://updates.jenkins.io/download/plugins/gitlab-plugin/ is also missing... something is going on very strange On 6 July 2017 at 02:26, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > Yes, very strange.. seems to be missing from upstream too

Re: [Proposal] Making all things Stapler more declarative

+jenkins-dev On 5 July 2017 at 02:13, Ullrich Hafner <ullrich.haf...@gmail.com> wrote: > > Am 04.07.2017 um 18:44 schrieb Stephen Connolly < > stephen.alan.conno...@gmail.com>: > > Ulli, > > What do you think on this proposal, given that you have contact with

Re: [Proposal] Making all things Stapler more declarative

Actually I nearly forgot Oleg you were driving the Google summer of code last year, what do you think? On Tue 4 Jul 2017 at 17:44, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Ulli, > > What do you think on this proposal, given that you have contact with a lot &g

Re: [Proposal] Making all things Stapler more declarative

Ulli, What do you think on this proposal, given that you have contact with a lot of students who have been trying to get to grips with the Jenkins code base. Would it make their task easier? -Stephen On 3 July 2017 at 05:21, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: &g

[Proposal] Making all things Stapler more declarative

I have been developing Jenkins plugins and changes to Jenkins core for more than 10 years now. As such, I have internalized a lot of the knowledge about how to develop against Jenkins and more specifically against Stapler. When I talk to people trying to start out development against Jenkins, the

Anyone else seeing a -SNAPSHOT deployed as a release for gradle plugin?

​ -- 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 this discussion on the web visit

Re: Cannot upload plugin to release repository, while shapshot works

Are you listed in the plugin repository permissions? if not file a PR against https://github.com/jenkins-infra/repository-permissions-updater/ On 27 June 2017 at 07:16, Tomasz Jurkiewicz wrote: > Hi, > > I get 401/Unauthorised upon uploading to release repository: >

Re: GitHub and Bitbucket branch source UI refactoring

d storm only on indexing" situation. > > > Den fredag den 23. juni 2017 kl. 15.32.54 UTC+2 skrev Stephen Connolly: >> >> How do you find the new UI compared with the previous one? >> >> On 23 June 2017 at 14:18, Joseph P <jose...@gmail.com> wro

Re: GitHub and Bitbucket branch source UI refactoring

look better now > with the new version." I used the plugin versions that Stephen originally > posted on June 20, but I take Michael's comment to mean there might be > newer versions. Please make this irrelevant by issuing release versions of > these plugins this week. :) > > Tha

Re: GitHub and Bitbucket branch source UI refactoring

ersions that Stephen originally >> posted on June 20, but I take Michael's comment to mean there might be >> newer versions. Please make this irrelevant by issuing release versions of >> these plugins this week. :) >> >> Thanks a ton! >> -KB >> >> On Frid

Re: GitHub and Bitbucket branch source UI refactoring

Phew! I found the bug in structs... and it is an easy fix... https://issues.jenkins-ci.org/browse/JENKINS-45130 so no renaming of classes required! On 25 June 2017 at 01:49, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > TL;DR keep the alpha's to throw-away instance

Re: GitHub and Bitbucket branch source UI refactoring

TL;DR keep the alpha's to throw-away instances until I identify whether I need to rename classes before the beta On Sun 25 Jun 2017 at 09:20, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > I have found an issue with how these plugins get their pipeline snippets > genera

Re: GitHub and Bitbucket branch source UI refactoring

I have found an issue with how these plugins get their pipeline snippets generated when all are installed an the same instance at the same time. Hopefully this is just a bug in the structs plugin and I can fix it there... BUT if I cannot fix it in structs I WILL HAVE TO RENAME CLASSES before a

Re: Question: Git Branch Source and the traits / behaviours

On 23 June 2017 at 17:43, Jesse Glick <jgl...@cloudbees.com> wrote: > On Fri, Jun 23, 2017 at 9:29 AM, Stephen Connolly > <stephen.alan.conno...@gmail.com> wrote: > > That means we would have to grandfather in the discovery of branches. > > > > So if we read

Re: Question: Git Branch Source and the traits / behaviours

On 23 June 2017 at 17:46, Jesse Glick wrote: > …or, if and when implementing that RFE, introduce a single trait > “Customize Discovered References” which would have its own checkboxes > for branches, tags, and maybe even some sort of pattern match for refs > or whatever. >

Re: Question: Git Branch Source and the traits / behaviours

On 23 June 2017 at 17:43, Jesse Glick <jgl...@cloudbees.com> wrote: > On Fri, Jun 23, 2017 at 9:29 AM, Stephen Connolly > <stephen.alan.conno...@gmail.com> wrote: > > That means we would have to grandfather in the discovery of branches. > > > > So if we read

Re: GitHub and Bitbucket branch source UI refactoring

aluate(Expression >> Factory2.java:74) >> at org.apache.commons.jelly.parser.EscapingExpression.evaluate( >> EscapingExpression.java:24) >> at org.apache.commons.jelly.impl.ExpressionScript.run(Expressio >> nScript.java:66) >> at org.apache.commons.jelly.impl.Scr

Re: Question: Git Branch Source and the traits / behaviours

er traits will > join in. > So take the migration part now. > > And if your need more vertical space, just flip your monitor into > porTrait.. pun intended. :D > > > Den fredag den 23. juni 2017 kl. 15.29.20 UTC+2 skrev Stephen Connolly: >> >> So before we cut a GA r

Re: Question: Git Branch Source and the traits / behaviours

On 23 June 2017 at 14:50, Mark Waite <mark.earl.wa...@gmail.com> wrote: > > > On Fri, Jun 23, 2017 at 7:29 AM Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> So before we cut a GA release of the JENKINS-43507 changes I thought it >> might

  1   2   3   4   5   6   7   >