[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [dtp-dev] Push tag in Git repo

Hi Fitz,

Each database enablement (IBM, MySQL, Oracle, etc.) has its own releng project with just those plugins now.  The thinking is that enablement developers should only have to get the repository containing  the specific enablement plugins they are interested in.

Regards,
Brian

Brian Payton

DTP PMC Lead
Data Tools Development
IBM Silicon Valley Laboratory





From:        Brian Fitzpatrick <bfitzpat@xxxxxxxxxx>
To:        DTP development mailing list <dtp-dev@xxxxxxxxxxx>
Date:        08/15/2011 09:33 AM
Subject:        Re: [dtp-dev] Push tag in Git repo
Sent by:        dtp-dev-bounces@xxxxxxxxxxx




Ok, so going back to this...

Yes, I can check it out as a general plug-in, but the general enablement releng project map file only has one line:

plugin@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=GIT,tag=v201004070709,repo=git://git.eclipse.org/gitroot/datatools/org.eclipse.datatools.enablement.general.git,path=plugins/org.eclipse.datatools.enablement.jdt.classpath

Where are the rest of the enablement projects listed?

_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat

----- Original Message -----
From: "Brian Payton" <bpayton@xxxxxxxxxx>
To: "DTP development mailing list" <dtp-dev@xxxxxxxxxxx>
Sent: Friday, August 12, 2011 12:03:00 PM
Subject: Re: [dtp-dev] Push tag in Git repo


Hi Fitz,

Here's some steps for tagging.


   1. Do a "Show in History" action on the plugin.
   2. Right-click on the change in the History view you want to tag and do a Team -> Create Tag... action. Enter a tag name following our usual practice and a tag comment. Leave everything else as default. Click OK. A yellow tag marker should show up in the History view on the entry for the code change.
   3. Make sure you have the correct releng project for the changed plugin in your workspace.
   4. Edit the .map file and update the tag for the changed plugin.
   5. Commit the change
   6. Do a Team -> Remote -> Push following Yong Jiang's recommendation

The reason you can't import the releng project is that it doesn't have a .project file associated with it. Use the "Import as General Project" option in the Import Projects wizard; that will create a .project file for you when it imports. Add the .project file to source control and check it in with your change. (I've been doing that for the enablement projects that I'm updating.)

Regards,
Brian

Brian Payton
DTP PMC Lead
Data Tools Development
IBM Silicon Valley Laboratory





From: Brian Fitzpatrick <bfitzpat@xxxxxxxxxx>
To: DTP development mailing list <dtp-dev@xxxxxxxxxxx>
Date: 08/12/2011 10:07 AM
Subject: Re: [dtp-dev] Push tag in Git repo
Sent by: dtp-dev-bounces@xxxxxxxxxxx




Yong, can you remind me how to tag a plug-in after a commit, or better yet what the steps are to the commit, tag, update map file, push process we're using now?

Plus, couple of questions about the map plugins.

1) I am unable to import the releng plugin from the enablement.general git repo in the master branch. Is it a valid project?
2) I'm not seeing a related releng plugin for the 1.9 branch - does one need to be created? I have some enablement fixes to deliver and can't seem to find the enablement map file.

Thanks
--Fitz

_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat

----- Original Message -----
From: "Yong Jiang" <yjiang@xxxxxxxxxxx>
To: dtp-dev@xxxxxxxxxxx
Sent: Friday, August 12, 2011 2:36:02 AM
Subject: [dtp-dev] Push tag in Git repo





By default, the 'git push' doesn â t transfer tags to remote servers.

You will have to explicitly push tags to remote repo after you tag the plugins and update map file. Otherwise DTP build will fail.



Command line:

git push origin v201108120600



EGit UI:

Team -> Remote -> Push...

Click 'Add All Tags Spec' in Push dialog

cid:image001.png@xxxxxxxxxxxxxxxxx





Thanks.

Yong Jiang.
_______________________________________________
dtp-dev mailing list
dtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dtp-dev
_______________________________________________
dtp-dev mailing list
dtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dtp-dev


_______________________________________________
dtp-dev mailing list
dtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dtp-dev
_______________________________________________
dtp-dev mailing list
dtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dtp-dev