Oh cool, I didn't know about that feature.
On Fri, Feb 7, 2020 at 5:35 PM James Nord wrote:
> >With jira, I'm either auto assigned the issue due to whatever component
> was first picked, or nothing at all. Groups of maintainers can't be
> notified. Un-assigned tickets don't get notified
>
> crea
>With jira, I'm either auto assigned the issue due to whatever component was
>first picked, or nothing at all. Groups of maintainers can't be notified.
>Un-assigned tickets don't get notified
create a filter that matches things you want to be notified for.
subscribe to that filter in
https://is
I tried emailing in a separate email outside the list. Thanks for CCing
them. I didn't make a PR, but I have been running a local build of this
plugin with this PR#1 for several years. Just want to get this merged and
get volunteer to support/maintain this and other plugins.
On Fri, Feb 7, 2020
I also really want to see issues.jenkins go away, but mostly due to how
slow it is. I don't think cloud is a lot better, but way less maintenance
for people.
I think the big push in the past for jira was because you couldn't migrate
issues between repos before in github. That got changed.. though
> On 7. Feb 2020, at 15:56, James Nord wrote:
>
> it kills me every time I need to file an issue and try and work out where it
> is to be reported and I consider myself knowledgeable about Jenkins and it's
> plugins.
I mentioned it in a previous response, but here's the link:
https://git
> On 2. Feb 2020, at 12:13, Tim Jacomb wrote:
>
> • Much easier to be a co-maintainer, with JIRA only the ‘component
> lead’ gets notified by default, you _can_ create your own filters and
> subscriptions, but it’s a lot more effort and most people (including me)
> don’t do that.
At
Technically we could migrate all issues to github, at least I saw some python
scripts doing that. I would be more concerned by the security issues, so indeed
we could also have both tools in place where most of the things are on github
issues
---
gpg --keyserver keys.gnupg.net --recv-key 52210
If anyone wants to help out there’s a progress page here:
https://jenkins-wiki-exporter.jenkins.io/progress
Pick one that isn’t in progress,
Use the wiki exporter to get all content and images,
Do a bit of cleanup
Open a pull request
Add your pull request to the GitHub project tracking it (
https
I generally agree with Ulli's comments.
so far we are all talking about the developer experience when interacting with
issues. we need to also think of the user experience to Jenkins users too. it
kills me every time I need to file an issue and try and work out where it is to
be reported and
For maintaining history, I've done something similar in the past when
migrating a project from codeplex to GitHub. The script I had migrated the
comments and the attachments as best it could. I could try a proof of
concept of people are interested.
On Fri, Feb 7, 2020, 07:06 Jesse Glick wrote:
>
Indeed congrats to everybody, this sub-project is a beautiful example of
contributing to an OSS project is not only about write code for the application
itself but also improving its ecosystem through collaboration.
---
gpg --keyserver keys.gnupg.net --recv-key 52210D3D
---
On Fri, Feb 7, 2020
On Fri, Feb 7, 2020 at 8:50 AM Olblak wrote:
> We migrate from Jira to Jira Cloud
> We migrate from Jira to Github Issues
Can we migrate to Jira Cloud with history intact, _and_ encourage use
of GitHub issues for new components?
--
You received this message because you are subscribed to the Goo
Gavin Mogan has made significant improvements to
https://plugins.jenkins.io/ . It loads faster, works better, and is easier
to maintain. Thanks Gavin!
As part of those improvements, plugin pages on the Jenkins wiki are now
automatically redirected to https://plugins.jenkins.io/ . For example
On Thu, Feb 6, 2020 at 8:10 AM Tomasz Markiewicz
wrote:
> I was wondering if it is possible to "integrate" heavy-job-plugin
> functionality into pipeline projects.
Not easily. See JENKINS-41940. The non-Pipeline functionality relies
on a core API (`JobProperty.getSubTasks`) which I am guessing w
Maintaining issues.jenkins-ci.org is time-consuming, and it's hard to find
someone who wants to do it.
While I totally agree that we shouldn't use multiple ticket system, I don't see
real good solution he
re
We migrate from Jira to Jira Cloud
-> We keep the history
-> No maintenance
-> We can on
Any other opinions?
So far we have 3 +1, and 1 -1
This isn't asking that we move everything over, but make it easier for new
plugin maintainers to use GitHub issues.
Thanks
Tim
On Mon, 3 Feb 2020 at 13:06, Chris Kilding
wrote:
> I'm inclined to agree with Joseph and Tim.
>
> When maintaining
How did you contact the current maintainer? I've CC'd the two emails I
found in recent commits. Did you make a public PR/Issue somewhere and at
ping them at all? Usually we start the 2 week countdown from the time of
the mailing list / cc.
On Fri, Feb 7, 2020 at 12:11 AM John Lengeling
wrote:
>
I would like volunteer as a plugin maintainer for the "OfflineOnFailure"
jenkins plugin. I use this plugin at work. There is a PR that I would
like to get merged so I don't have to keep using a custom/snapshot version
of the plugin. Also this is a simple plugin which I hope to get more
exp
18 matches
Mail list logo
