rce-plugin. All
>> issues will be moved to p4-plugin
>>
>> Lemme know if that works.
>>
>> Gavin
>>
>> On Tue., Dec. 10, 2019, 3:14 p.m. Rob Petti, wrote:
>>
>>> Hey folks,
>>>
>>> As per the subject, can we please delete th
Hey folks,
As per the subject, can we please delete the perforce-plugin component from
Jenkins' Jira? It's been deprecated for years now, but folks are still
accidentally filing tickets against it instead of p4-plugin.
If we can't delete it, can we change the default assignee to "Unassigned"?
Have you released it already? If so, it takes up to 6 hours to show up in
the update center. If not, then that would be why.
On Mon, Jul 7, 2014 at 8:30 AM, Paul Allen pal...@perforce.com wrote:
It seems the p4-plugin project is not showing up in the update centre?
I forgot to add the wiki
, the plugin's Display Name is Perforce Plugin, hence there can be
various conflicts.
I'd recommend to change the display name
2014-07-07 18:31 GMT+04:00 Rob Petti rob.pe...@gmail.com:
Have you released it already? If so, it takes up to 6 hours to show up
in the update center
?
I was going to attempt a release under a new 'jenkinsci/p4-plugin' to
avoid the migration issues and use of the beta update centre. If I can
work out a migration route for old build Jobs then I could look to merge
the two plugins together.
Paul
On 3 Jul 2014, at 16:37, Rob Petti rob.pe
Let's start with actually uploading it to github. Just create a new project
on your account and push the source to it.
Oleg, it sounds like having it in the same namespace might not be ideal
after all? Would you prefer to have it as a separate plugin entirely?
On Friday, 13 June 2014 11:46:50
base and give the opportunity for a clean start.
Paul
On 17 Apr 2014, at 19:23, Rob Petti rob@gmail.com wrote:
I thought it was decided that refactoring the old plugin was the
better way to go? It's less of an impact on users, and preserves all of the
required functionality
for your involvement, I'm pleased there is so much interest
and help.
Kind regards,
Paul
On 18 Apr 2014, at 18:46, Rob Petti rob.pe...@gmail.com wrote:
I didn't realize that you could release two versions of a plugin at the
same time to two different update centers. I think your proposal
would be less disruptive to the existing
user base and give the opportunity for a clean start.
Paul
On 17 Apr 2014, at 19:23, Rob Petti rob.pe...@gmail.com wrote:
I thought it was decided that refactoring the old plugin was the better
way to go? It's less of an impact on users, and preserves
I thought it was decided that refactoring the old plugin was the better way
to go? It's less of an impact on users, and preserves all of the required
functionality.
If not, then just make a new repo, I guess...
On Thursday, 17 April 2014 10:52:20 UTC-6, pallen wrote:
I have been discussing
I suspect this issue has returned...
On Wed, Dec 11, 2013 at 6:14 PM, Kohsuke Kawaguchi k...@kohsuke.org wrote:
Reindex failure due to OOME caused a problem. I rerun it to the completion
and things are now back to normal.
2013/12/11 Jesse Glick jgl...@cloudbees.com
Is it just me or is
Hey all
Has anyone else noticed if email notifications from our jira have stopped
working? I've missed several updates that should have been emailed to me,
but my inbox and spam folders are both empty, so I'm starting to suspect an
issue with the server.
~Rob
--
You received this message
perforce-plugin.git has been restored from my local copy.
It may be beneficial to look into implementing finer grained access control
for individual repos. For example, I thought that only myself, Oleg, and
the Jenkins project owners had write access to the perforce plugin. If
everyone has
Love it!
On Thursday, 19 April 2012 10:01:26 UTC-6, Kohsuke Kawaguchi wrote:
Following up the conversation from JUC Paris, I pushed the publisher
branch to the repository that changes the publisher configuration UI.
I'd like to get feedback on whether people think this is a good idea
or a
14 matches
Mail list logo
