Hi Damien,
Did this lead to anything? The CI servers resources seem to be already
exhausted with a few PRs to ATH.
/James
On Monday, September 20, 2021 at 8:25:12 AM UTC+1 damien@gmail.com
wrote:
> Hello there ! We (the Jenkins admin) we'll try to add more capability for
> the month of
Hi Jamie,
incase you are not aware, there are a few acceptance tests for the Job DSL
plugin that have been failing for a while. If you would like to pick them
up to ensure the plugin stays healthy that would be great!
https://ci.jenkins.io/job/Core/job/acceptance-test-harness/job/master/lastCo
Hi all,
CloudBees has a number of plugins in jenkins-ci organisation that we are
maintainers of.
Currently when our internal teams change we need to modify multiple GitHub
repo settings and associated permissions RPU. This is cumbersome (and
error prone) for us, and for the reviewers of the R
Hi all,
So thanks Baptiste for creating the team which I now have maintainership of
so can add users.
One issue I have is that users that are not currently a member of the
jenkinsci organisation can not be added to the team.
I guess normally adding a user to a plugin group via IRC would also
there is possibility of something part way between the current CD flow (no
junk pushes) and m-r-p.
m-r-p does not have to just take the current version and remove snapshot
and increment the last digit, nor does it need to push the commits back
(just the tag) (which I believe are your main objec
>> Using MRP as I described would not confuse any tool
>Depends on the tool. The problem would be that a source checkout at the
commit/tag would, if loaded as a project rather than a deployed artifact,
have a version different from the artifact. (Also true in JEP-229
components by default, but
The only issue I would have in early removal is if a plugin dropped
compatability whilst it was still supported for a supported LTS version,
that said we have no stake in what a plugin does or does not do. So I
guess I have no issue with dropping IE today and promoting Edge to T1.
it could mak
> There's been a request for https://issues.jenkins.io/browse/JENKINS-67635 to
be backported
> Just merged in https://github.com/jenkinsci/jenkins/pull/6193
Given this area code area has proved to be a hot potato and the fix is not
in a weekly yet, I would be hesitant to say "go for it" on thi
> Thanks, James. For the login plugin we have a pinned dependency in our
pom.xml, so we plan on updating that so folks get a fixed version of Mailer
if that isn't present on their Jenkins instance.
you do not need to do that - they would get a fixed version of mailer if it
was not installed on
> While I understand the reasoning for using the latest patch version of
an LTS I think this increases the number of unneeded version upgrades for
plugin authors.
warning: unpopular optinion follows
as does accepting *any* update to the BOM in your plugin when you do not
need a new API provi
Hi all,
A point raised in a permission update for a plugin in RPU is that we are
still granting users permission to Artifactory for deployment of a plugin
that they maintain even if the plugin is using CD.
https://github.com/jenkins-infra/repository-permissions-updater/pull/2265/files#r7739142
I found https://issues.jenkins.io/browse/JENKINS-67885 and have filed
https://github.com/jenkinsci/jenkins/pull/6305
On Wednesday, February 23, 2022 at 6:20:09 PM UTC Cathy Chan wrote:
> Hello everyone,
>
> Latest LTS RC was made public and it is ready to be tested. Final release
> is schedul
s this also used for the windows agents?
I just merged a PR that had a passing CI only for master to fail
C:\Jenkins\workspace\ns_promoted-builds-plugin_master\target\tmp\j
h5732164843774452221\workspace\test1>powershell -command "Invoke-WebRequest
http://localhost:49491/jenkins/job/up/lastSucce
What do we need to do to formalize this? Is it just a case of
a https://github.com/jenkins-infra/helpdesk ticket or something else?
Regards
/James
On Monday, February 14, 2022 at 9:30:21 AM UTC timja...@gmail.com wrote:
> Sounds good to move it to Jenkinsci very few usages by the looks of it:
Going back to the earlier premise
> It seems to me that a number of problems are caused by ATH tests being
in a separate repository from the code under test
I would say the biggest problem is not so much that - rather that we do not
run enough of these tests for the code that is affected, early
Hi Ulli,
Can you clarify what these guidelines are and where they are (I did not see
anything in a scan of the ML, nor on jenkins.io)?
With my Jenkins user hat on I would be somewhat annoyed if I had to upgrade
Jenkins to get a small bug fix for a plugin.
Upgrading to every `.1` LTS is ok -
https://groups.google.com/g/jenkinsci-dev/c/9sZipk1PHns/m/mqtV7K8uAAAJ
would report there is the opposite.
Whilst Jira is a PITA, GitHub issues for me has more drawbacks.
We seem to be missing some improvements to Jira that would make it much
nicer day to day,
e.g.
https://confluence.atlassian
022 at 10:38:36 AM UTC+1 ullrich...@gmail.com wrote:
> Am 13.06.2022 um 11:11 schrieb 'jn...@cloudbees.com' via Jenkins
> Developers :
>
> Hi Ulli,
>
> Can you clarify what these guidelines are and where they are (I did not
> see anything in a scan of the ML, nor o
itHub, many people
> struggle to report issues.
>
> I have started writing a draft JEP to put some more words together but
> interested in any feedback on the above.
> (I'm aware EPIC links are not included in the export, I plan to fix that)
> (Web links exporting doesn'
HI James
Have your test setup works ok before you introduced vault (ie with the
standard credential helper?).
I would hazard a guess that your git installation was installed and
configured to use a credential helper.
git config --system --unset credential.helper
Regards
/James
On Monday
Hi all
Just released a plugin and I have the following warning
[WARNING] javadoc: warning - Error fetching URL: https://javadoc.jenkins.io/
The javadoc for jenkins was recently switch to Java11 (seems a week early)
and this means that plugins can no longer link correctly when
compiling/releasi
t; Can you tell if the javadoc was published for the plugin or if there's any
> issue with it?
>
> We can test it out on the test plugin
> <https://github.com/jenkinsci/jenkins-infra-test-plugin> to not impact
> users.
>
> Thanks
> Tim
>
> On Tue, 14 Jun
I am seeing some issues with the actual jenkins java11 javadoc too. Smells
like bugs in javadoc - but it may be out invocation of it is not correct.
The search seems to be broken - when you follow a link to a type you get
linked to a page that starts https://javadoc.jenkins.io/undefined
e.g.
Good find Basil,
the above issue I mentioned with search seems to
be https://bugs.openjdk.org/browse/JDK-8215291 which is alas also fixed in
Java 12
Stack overflow[1] mentions some workarounds, but they appear to have other
issues.
/James
[1]
https://stackoverflow.com/questions/5232631
HI,
If I understand your question correctly, you just need to return non-null
for getDisplayName and getIconFileName in your Action[1]
/James
[1] https://javadoc.jenkins.io//hudson/model/Action.html
On Thursday, June 16, 2022 at 12:17:40 AM UTC+1 mukhammadno...@gmail.com
wrote:
> Is there an
Hi,
> - could it be because I'm running on Gradle?
:-) well you are in the minoroty and the least tested path.
However I do not see any dependency for cloudbees-folder
in
https://github.com/jenkinsci/job-dsl-plugin/blob/defect/org-folder-secrets/build.gradle#L21-L27
(but I admit I am not
> But this chain of reasoning led me to another conclusion as well: if
we can hide SLF4J, then why not also hide Bouncy Castle in similar
fashion? (Context: Bouncy Castle is the only obvious way to implement
the --httpsPrivateKey and --httpsCertificate options for Java 17,
since the Java Platform
Hi all,
Does anyone use the HTMLUnit browser in the jenkins acceptance-test-harness
suite?
I am doing some cleaning and I know that chrome and firefox are used, but
looking at the others also.
I think it is safe to nuke InternetExplorer support from orbit, and I would
be amazed if HTMLUnit ac
the package names are still the same as far as I understand, and this would
still have issues due to the nature of the dependencies.
as k8s has dependencies on both -creds and -api if the creds where updated
to use the new -6-api when the classess that k8s would see would be a bit
"iffy" would
> I've built a series of plugin incremental builds with this new version. I
believe I am covering all existing plugins in the Jenkins OSS ecosystem
using this library. All existing tests are passing.
kubernetes-credential-provider uses the api.
/James
On Thursday, January 5, 2023 at 6:58:30 PM
Hi all,
When modernising a plugin I find the tedious part is to create all the
labels for both CD releases and the release notes.
it's time consuming to find a reference repo and then duplicate the labels
(and their colours) to the repo I am updating.
As this is not an uncommon task I was wond
Please do not troll this out
until https://github.com/diffplug/spotless/issues/1559 is fixed - this
causes all code to fail for windows users using checkout-as-is and
checkin-as-is which is not uncommon for windows users who also share code
with the Linux subsytem for windows.
I have battled t
> Please do not troll
that too but I meant roll this out.
On Wednesday, April 12, 2023 at 2:06:02 PM UTC+1 jn...@cloudbees.com wrote:
> Please do not troll this out until
> https://github.com/diffplug/spotless/issues/1559 is fixed - this causes
> all code to fail for windows users using checkou
2.414 has a regression in the plugin manager.
I would be -1 on this unless that is fixed (currently missing a Jenkins bug
but has been the cause of a lot of ATH failures)
https://github.com/jenkinsci/acceptance-test-harness/issues/1284 for the
current status/investigation, I will file a Jenkins
g in 2.414 has been fixed.
>
> On Sat, 22 Jul 2023 at 00:21, Basil Crow wrote:
>
>> On Fri, Jul 21, 2023 at 10:42 AM 'jn...@cloudbees.com' via Jenkins
>> Developers wrote:
>> > 2.414 has a regression in the plugin manager.
>> > I would be -1 on thi
t;> version they were introduced in I think)?
>>
>> The plugin manager bug in 2.414 has been fixed.
>>
>> On Sat, 22 Jul 2023 at 00:21, Basil Crow wrote:
>>
>>> On Fri, Jul 21, 2023 at 10:42 AM 'jn...@cloudbees.com' via Jenkins
>>> Devel
Hi Gavin,
I just tried this now and it failed with "GraphqlError: Nullability
mismatch on variable $color1 and argument color (String / String!)"
/James
On Friday, March 31, 2023 at 3:58:49 PM UTC+1 ga...@gavinmogan.com wrote:
> I made https://plugins-self-service-3ir4b.ondigitalocean.app/ a wh
Hi all,
the j-interop and jcifs libraries only appear to be used for very narrow
use cases
1. The ability to install Jenkins as a service[1] when it is running (by
java -jar) on a windows machine
2. for installing windows agents via dcom etc (which is deprecated[2])
There are a couple of uses
> 1. The ability to install Jenkins as a service[1] when it is running (by
java -jar) on a windows machine
I forgot to mention - which potentially valid - I would argue that the user
should just download the MSI package for this instead, afterall we do not
attempt to install a systemd file when
39 matches
Mail list logo
