ClearCase plugin using dynamic views

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

ClearCase plugin using dynamic views

mezlight
It seems like the dynamic view is being updated with the config spec identified within the ClearCase plugin configuration.  I thought the concept was to use the existing dynamic view and not update the config spec.  I live in a build world that the config spec changes every other day (interfaces) and it would be nice to use the dynamic views config spec as is (maybe an option to the plugin configuration).  That way the owner (a common user) of the view can modify the config spec and not the actual hudson project every time there is a change.  
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ClearCase plugin using dynamic views

mezlight
Is the dynamic view only used for Windows?  When trying to use dynamic views from a Unix world there is a parsing error in setting the config spec.  The config spec file created by the ClearCase plugin should not have any ^M characters or else you will get a parsing error.

mezlight wrote
It seems like the dynamic view is being updated with the config spec identified within the ClearCase plugin configuration.  I thought the concept was to use the existing dynamic view and not update the config spec.  I live in a build world that the config spec changes every other day (interfaces) and it would be nice to use the dynamic views config spec as is (maybe an option to the plugin configuration).  That way the owner (a common user) of the view can modify the config spec and not the actual hudson project every time there is a change.  
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ClearCase plugin using dynamic views

Erik Ramfelt
In reply to this post by mezlight
On Dec 12, 2007 5:07 PM, mezlight <[hidden email]> wrote:
>
> It seems like the dynamic view is being updated with the config spec
> identified within the ClearCase plugin configuration.  I thought the concept
> was to use the existing dynamic view and not update the config spec.  I live
> in a build world that the config spec changes every other day (interfaces)
> and it would be nice to use the dynamic views config spec as is (maybe an
> option to the plugin configuration).  That way the owner (a common user) of
> the view can modify the config spec and not the actual hudson project every
> time there is a change.

Yes, the plugin sets the config spec of the dynamic view, and if the
config spec of the job changes (or the config spec changes in the
view) it will update the config spec in the dynamic view. The only
difference for the plugin between a dynamic and a snapshot view is
that the plugin can not create dynamic views (and that it will not do
"cleartool update"). The idea was that the dynamic view should be
governed by the plugin and its config spec. That way it was simpler
for our administrators to manage the dynamic views on machines, in our
test lab, and then rebuild using a different config spec. Perhaps this
should be better described in the documentation.

I dont really understand your problem that the dynamic view is updated
with a new config spec. If someone needs to change the config spec,
then they could do it through Hudson and then rebuild. Or am I missing
something here?

regards
//Erik

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ClearCase plugin using dynamic views

Erik Ramfelt
In reply to this post by mezlight
Oh, Ive tested the dynamic view on Windows only as we dont have any
unix machines at work. The dynamic view feature should work on all
OSes, so this is a bug. Could you report it to the issue tracker?

Are you running the Hudson master server on a Windows machine? Or does
Hudson add "\r\n" to all text boxes even on linux?

Regards
//Erik

On Dec 12, 2007 5:52 PM, mezlight <[hidden email]> wrote:

>
> Is the dynamic view only used for Windows?  When trying to use dynamic views
> from a Unix world there is a parsing error in setting the config spec.  The
> config spec file created by the ClearCase plugin should not have any ^M
> characters or else you will get a parsing error.
>
>
> mezlight wrote:
> >
> > It seems like the dynamic view is being updated with the config spec
> > identified within the ClearCase plugin configuration.  I thought the
> > concept was to use the existing dynamic view and not update the config
> > spec.  I live in a build world that the config spec changes every other
> > day (interfaces) and it would be nice to use the dynamic views config spec
> > as is (maybe an option to the plugin configuration).  That way the owner
> > (a common user) of the view can modify the config spec and not the actual
> > hudson project every time there is a change.
> >
>
> --
> View this message in context: http://www.nabble.com/ClearCase-plugin-using-dynamic-views-tp14298247p14299126.html
>
> Sent from the Hudson users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ClearCase plugin using dynamic views

mezlight
In reply to this post by Erik Ramfelt

eramfelt wrote
On Dec 12, 2007 5:07 PM, mezlight <Jason.Messmer@xerox.com> wrote:
>
> It seems like the dynamic view is being updated with the config spec
> identified within the ClearCase plugin configuration.  I thought the concept
> was to use the existing dynamic view and not update the config spec.  I live
> in a build world that the config spec changes every other day (interfaces)
> and it would be nice to use the dynamic views config spec as is (maybe an
> option to the plugin configuration).  That way the owner (a common user) of
> the view can modify the config spec and not the actual hudson project every
> time there is a change.

>Yes, the plugin sets the config spec of the dynamic view, and if the
>config spec of the job changes (or the config spec changes in the
>view) it will update the config spec in the dynamic view. The only
>difference for the plugin between a dynamic and a snapshot view is
>that the plugin can not create dynamic views (and that it will not do
>"cleartool update"). The idea was that the dynamic view should be
>governed by the plugin and its config spec. That way it was simpler
>for our administrators to manage the dynamic views on machines, in our
>test lab, and then rebuild using a different config spec. Perhaps this
>should be better described in the documentation.

>I dont really understand your problem that the dynamic view is updated
>with a new config spec. If someone needs to change the config spec,
>then they could do it through Hudson and then rebuild. Or am I missing
>something here?

>regards
> //Erik
Yeah I know it should be govern through Hudson but I was just thinking if
I am using a dynamic view created prior to the project then it would be easier to
update the view from the command line (I am always in that environment) then going
through Hudson (which is simple enough).  The dilemma that I have is my config specs
change a lot and I need a way to update the config spec automatically.  Prior to using Hudson,
I have an automated process that will do this for me.  I think there should be an option in the ClearCase
plugin to allow the user to use this view and and nothing else (don't create it, don't update it, don't
do anything except use it).

~Jason

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@hudson.dev.java.net
For additional commands, e-mail: users-help@hudson.dev.java.net
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ClearCase plugin using dynamic views

anubhav.berry
Windows adds ^M characters as spare characters for the carriage return
character. You may have to strip these characters at the UNIX end.

I found a good conversation for the same at the following link:

http://lists.gnupg.org/pipermail/gnupg-users/2002-November/015809.html

I hope this helps



                                                                           
             mezlight                                                      
             <Jason.Messmer@xe                                            
             rox.com>                                                   To
                                       [hidden email]          
             13/12/2007 05:15                                           cc
             AM                                                            
                                                                   Subject
                                       Re: ClearCase plugin using dynamic  
             Please respond to         views                              
             [hidden email].                                            
                 java.net                                                  
                                                                           
                                                                           
                                                                           
                                                                           







eramfelt wrote:

>
> On Dec 12, 2007 5:07 PM, mezlight <[hidden email]> wrote:
>>
>> It seems like the dynamic view is being updated with the config spec
>> identified within the ClearCase plugin configuration.  I thought the
>> concept
>> was to use the existing dynamic view and not update the config spec.  I
>> live
>> in a build world that the config spec changes every other day
>> (interfaces)
>> and it would be nice to use the dynamic views config spec as is (maybe
an

>> option to the plugin configuration).  That way the owner (a common user)
>> of
>> the view can modify the config spec and not the actual hudson project
>> every
>> time there is a change.
>
>>Yes, the plugin sets the config spec of the dynamic view, and if the
>>config spec of the job changes (or the config spec changes in the
>>view) it will update the config spec in the dynamic view. The only
>>difference for the plugin between a dynamic and a snapshot view is
>>that the plugin can not create dynamic views (and that it will not do
>>"cleartool update"). The idea was that the dynamic view should be
>>governed by the plugin and its config spec. That way it was simpler
>>for our administrators to manage the dynamic views on machines, in our
>>test lab, and then rebuild using a different config spec. Perhaps this
>>should be better described in the documentation.
>
>>I dont really understand your problem that the dynamic view is updated
>>with a new config spec. If someone needs to change the config spec,
>>then they could do it through Hudson and then rebuild. Or am I missing
>>something here?
>
>>regards
>> //Erik
> Yeah I know it should be govern through Hudson but I was just thinking if
> I am using a dynamic view created prior to the project then it would be
> easier to
> update the view from the command line (I am always in that environment)
> then going
> through Hudson (which is simple enough).  The dilemma that I have is my
> config specs
> change a lot and I need a way to update the config spec automatically.
> Prior to using Hudson,
> I have an automated process that will do this for me.  I think there
> should be an option in the ClearCase
> plugin to allow the user to use this view and and nothing else (don't
> create it, don't update it, don't
> do anything except use it).
>
> ~Jason
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
>

--
View this message in context:
http://www.nabble.com/ClearCase-plugin-using-dynamic-views-tp14298247p14300596.html

Sent from the Hudson users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


_____________________________________________________________________
This e-mail has been scanned for viruses by MCI's Internet Managed
Scanning Services - powered by MessageLabs. For further information
visit http://www.mci.com



***  PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS E_MAIL.  ***

AXA and AllianceBernstein: Winner of 'Morningstar Fund Manager of the Year
2006 - Australia'.
*********************************************************************************
Important Note
This email (including any attachments) contains information which is
confidential and may be subject to legal privilege.  If you are not
the intended recipient you must not use, distribute or copy this
email.  If you have received this email in error please notify the
sender immediately and delete this email. Any views expressed in this
email are not necessarily the views of AXA.   Thank you.
**********************************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ClearCase plugin using dynamic views

Erik Ramfelt
Ive committed a fix that will replace "\r\n" with "\n" in the config
spec when running on unix. Iit will be available at
http://hudson.ramfelt.se in 1 hour. If you have the chance, test it
and let me know how it went.


//Erik

On Dec 12, 2007 11:00 PM,  <[hidden email]> wrote:

> Windows adds ^M characters as spare characters for the carriage return
> character. You may have to strip these characters at the UNIX end.
>
> I found a good conversation for the same at the following link:
>
> http://lists.gnupg.org/pipermail/gnupg-users/2002-November/015809.html
>
> I hope this helps
>
>
>
>
>              mezlight
>              <Jason.Messmer@xe
>              rox.com>                                                   To
>                                        [hidden email]
>              13/12/2007 05:15                                           cc
>              AM
>                                                                    Subject
>                                        Re: ClearCase plugin using dynamic
>              Please respond to         views
>              [hidden email].
>                  java.net
>
>
>
>
>
>
>
>
>
>
>
>
> eramfelt wrote:
> >
> > On Dec 12, 2007 5:07 PM, mezlight <[hidden email]> wrote:
> >>
> >> It seems like the dynamic view is being updated with the config spec
> >> identified within the ClearCase plugin configuration.  I thought the
> >> concept
> >> was to use the existing dynamic view and not update the config spec.  I
> >> live
> >> in a build world that the config spec changes every other day
> >> (interfaces)
> >> and it would be nice to use the dynamic views config spec as is (maybe
> an
> >> option to the plugin configuration).  That way the owner (a common user)
> >> of
> >> the view can modify the config spec and not the actual hudson project
> >> every
> >> time there is a change.
> >
> >>Yes, the plugin sets the config spec of the dynamic view, and if the
> >>config spec of the job changes (or the config spec changes in the
> >>view) it will update the config spec in the dynamic view. The only
> >>difference for the plugin between a dynamic and a snapshot view is
> >>that the plugin can not create dynamic views (and that it will not do
> >>"cleartool update"). The idea was that the dynamic view should be
> >>governed by the plugin and its config spec. That way it was simpler
> >>for our administrators to manage the dynamic views on machines, in our
> >>test lab, and then rebuild using a different config spec. Perhaps this
> >>should be better described in the documentation.
> >
> >>I dont really understand your problem that the dynamic view is updated
> >>with a new config spec. If someone needs to change the config spec,
> >>then they could do it through Hudson and then rebuild. Or am I missing
> >>something here?
> >
> >>regards
> >> //Erik
> > Yeah I know it should be govern through Hudson but I was just thinking if
> > I am using a dynamic view created prior to the project then it would be
> > easier to
> > update the view from the command line (I am always in that environment)
> > then going
> > through Hudson (which is simple enough).  The dilemma that I have is my
> > config specs
> > change a lot and I need a way to update the config spec automatically.
> > Prior to using Hudson,
> > I have an automated process that will do this for me.  I think there
> > should be an option in the ClearCase
> > plugin to allow the user to use this view and and nothing else (don't
> > create it, don't update it, don't
> > do anything except use it).
> >
> > ~Jason
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/ClearCase-plugin-using-dynamic-views-tp14298247p14300596.html
>
> Sent from the Hudson users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
> _____________________________________________________________________
> This e-mail has been scanned for viruses by MCI's Internet Managed
> Scanning Services - powered by MessageLabs. For further information
> visit http://www.mci.com
>
>
>
> ***  PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS E_MAIL.  ***
>
> AXA and AllianceBernstein: Winner of 'Morningstar Fund Manager of the Year
> 2006 - Australia'.
> *********************************************************************************
> Important Note
> This email (including any attachments) contains information which is
> confidential and may be subject to legal privilege.  If you are not
> the intended recipient you must not use, distribute or copy this
> email.  If you have received this email in error please notify the
> sender immediately and delete this email. Any views expressed in this
> email are not necessarily the views of AXA.   Thank you.
> **********************************************************************************
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Re: ClearCase plugin using dynamic views

mezlight
It worked...Thanks...

On the another note, I would suggest to change "View drive" to "View
root" to be cross platform compliant with the following
help description from the ClearCase admin manual:

"Every dynamic view on a host is displayed as a subdirectory of the
host's view root directory.
On computers running Linux(R) or the UNIX(R) system, the default view
root directory is /view.
On Windows(R) computers, the default view root directory is \\view,
which is mapped by default to drive M."

For Unix, the user would have to specified /view as the view root and
M:\ for Windows if they
are using the standard default ClearCase settings.  Unless the view root
is specified, by default
you could have these as the default settings.

~Jay

 

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf
Of Erik Ramfelt
Sent: Wednesday, December 12, 2007 5:32 PM
To: [hidden email]
Subject: Re: ClearCase plugin using dynamic views

Ive committed a fix that will replace "\r\n" with "\n" in the config
spec when running on unix. Iit will be available at
http://hudson.ramfelt.se in 1 hour. If you have the chance, test it and
let me know how it went.


//Erik

On Dec 12, 2007 11:00 PM,  <[hidden email]> wrote:
> Windows adds ^M characters as spare characters for the carriage return

> character. You may have to strip these characters at the UNIX end.
>
> I found a good conversation for the same at the following link:
>
> http://lists.gnupg.org/pipermail/gnupg-users/2002-November/015809.html
>
> I hope this helps
>
>
>
>
>              mezlight
>              <Jason.Messmer@xe
>              rox.com>
To
>                                        [hidden email]
>              13/12/2007 05:15
cc
>              AM
>
Subject
>                                        Re: ClearCase plugin using
dynamic

>              Please respond to         views
>              [hidden email].
>                  java.net
>
>
>
>
>
>
>
>
>
>
>
>
> eramfelt wrote:
> >
> > On Dec 12, 2007 5:07 PM, mezlight <[hidden email]> wrote:
> >>
> >> It seems like the dynamic view is being updated with the config
> >> spec identified within the ClearCase plugin configuration.  I
> >> thought the concept was to use the existing dynamic view and not
> >> update the config spec.  I live in a build world that the config
> >> spec changes every other day
> >> (interfaces)
> >> and it would be nice to use the dynamic views config spec as is
> >> (maybe
> an
> >> option to the plugin configuration).  That way the owner (a common
> >> user) of the view can modify the config spec and not the actual
> >> hudson project every time there is a change.
> >
> >>Yes, the plugin sets the config spec of the dynamic view, and if the

> >>config spec of the job changes (or the config spec changes in the
> >>view) it will update the config spec in the dynamic view. The only
> >>difference for the plugin between a dynamic and a snapshot view is
> >>that the plugin can not create dynamic views (and that it will not
> >>do "cleartool update"). The idea was that the dynamic view should be

> >>governed by the plugin and its config spec. That way it was simpler
> >>for our administrators to manage the dynamic views on machines, in
> >>our test lab, and then rebuild using a different config spec.
> >>Perhaps this should be better described in the documentation.
> >
> >>I dont really understand your problem that the dynamic view is
> >>updated with a new config spec. If someone needs to change the
> >>config spec, then they could do it through Hudson and then rebuild.
> >>Or am I missing something here?
> >
> >>regards
> >> //Erik
> > Yeah I know it should be govern through Hudson but I was just
> > thinking if I am using a dynamic view created prior to the project
> > then it would be easier to update the view from the command line (I
> > am always in that environment) then going through Hudson (which is
> > simple enough).  The dilemma that I have is my config specs change a

> > lot and I need a way to update the config spec automatically.
> > Prior to using Hudson,
> > I have an automated process that will do this for me.  I think there

> > should be an option in the ClearCase plugin to allow the user to use

> > this view and and nothing else (don't create it, don't update it,
> > don't do anything except use it).
> >
> > ~Jason
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/ClearCase-plugin-using-dynamic-views-tp14298247p
> 14300596.html
>
> Sent from the Hudson users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
> _____________________________________________________________________
> This e-mail has been scanned for viruses by MCI's Internet Managed
> Scanning Services - powered by MessageLabs. For further information
> visit http://www.mci.com
>
>
>
> ***  PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS E_MAIL.  ***
>
> AXA and AllianceBernstein: Winner of 'Morningstar Fund Manager of the
> Year
> 2006 - Australia'.
> **********************************************************************
> ***********
> Important Note
> This email (including any attachments) contains information which is
> confidential and may be subject to legal privilege.  If you are not
> the intended recipient you must not use, distribute or copy this
> email.  If you have received this email in error please notify the
> sender immediately and delete this email. Any views expressed in this
> email are not necessarily the views of AXA.   Thank you.
> **********************************************************************
> ************
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Re: ClearCase plugin using dynamic views

Erik Ramfelt
Yes, you are right. It will be changed in the next version. And thanks
for the help description!

But, can you create snapshot views with the version you are currently
using? I replace all "\r\n" with "\n" for both dynamic and snapshot
views, and would like to know that it didnt break.

thanks
//Erik

On Dec 13, 2007 3:22 PM, Messmer, Jason <[hidden email]> wrote:

> It worked...Thanks...
>
> On the another note, I would suggest to change "View drive" to "View
> root" to be cross platform compliant with the following
> help description from the ClearCase admin manual:
>
> "Every dynamic view on a host is displayed as a subdirectory of the
> host's view root directory.
> On computers running Linux(R) or the UNIX(R) system, the default view
> root directory is /view.
> On Windows(R) computers, the default view root directory is \\view,
> which is mapped by default to drive M."
>
> For Unix, the user would have to specified /view as the view root and
> M:\ for Windows if they
> are using the standard default ClearCase settings.  Unless the view root
> is specified, by default
> you could have these as the default settings.
>
> ~Jay
>
>
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf
> Of Erik Ramfelt
> Sent: Wednesday, December 12, 2007 5:32 PM
> To: [hidden email]
>
> Subject: Re: ClearCase plugin using dynamic views
>
> Ive committed a fix that will replace "\r\n" with "\n" in the config
> spec when running on unix. Iit will be available at
> http://hudson.ramfelt.se in 1 hour. If you have the chance, test it and
> let me know how it went.
>
>
> //Erik
>
> On Dec 12, 2007 11:00 PM,  <[hidden email]> wrote:
> > Windows adds ^M characters as spare characters for the carriage return
>
> > character. You may have to strip these characters at the UNIX end.
> >
> > I found a good conversation for the same at the following link:
> >
> > http://lists.gnupg.org/pipermail/gnupg-users/2002-November/015809.html
> >
> > I hope this helps
> >
> >
> >
> >
> >              mezlight
> >              <Jason.Messmer@xe
> >              rox.com>
> To
> >                                        [hidden email]
> >              13/12/2007 05:15
> cc
> >              AM
> >
> Subject
> >                                        Re: ClearCase plugin using
> dynamic
> >              Please respond to         views
> >              [hidden email].
> >                  java.net
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > eramfelt wrote:
> > >
> > > On Dec 12, 2007 5:07 PM, mezlight <[hidden email]> wrote:
> > >>
> > >> It seems like the dynamic view is being updated with the config
> > >> spec identified within the ClearCase plugin configuration.  I
> > >> thought the concept was to use the existing dynamic view and not
> > >> update the config spec.  I live in a build world that the config
> > >> spec changes every other day
> > >> (interfaces)
> > >> and it would be nice to use the dynamic views config spec as is
> > >> (maybe
> > an
> > >> option to the plugin configuration).  That way the owner (a common
> > >> user) of the view can modify the config spec and not the actual
> > >> hudson project every time there is a change.
> > >
> > >>Yes, the plugin sets the config spec of the dynamic view, and if the
>
> > >>config spec of the job changes (or the config spec changes in the
> > >>view) it will update the config spec in the dynamic view. The only
> > >>difference for the plugin between a dynamic and a snapshot view is
> > >>that the plugin can not create dynamic views (and that it will not
> > >>do "cleartool update"). The idea was that the dynamic view should be
>
> > >>governed by the plugin and its config spec. That way it was simpler
> > >>for our administrators to manage the dynamic views on machines, in
> > >>our test lab, and then rebuild using a different config spec.
> > >>Perhaps this should be better described in the documentation.
> > >
> > >>I dont really understand your problem that the dynamic view is
> > >>updated with a new config spec. If someone needs to change the
> > >>config spec, then they could do it through Hudson and then rebuild.
> > >>Or am I missing something here?
> > >
> > >>regards
> > >> //Erik
> > > Yeah I know it should be govern through Hudson but I was just
> > > thinking if I am using a dynamic view created prior to the project
> > > then it would be easier to update the view from the command line (I
> > > am always in that environment) then going through Hudson (which is
> > > simple enough).  The dilemma that I have is my config specs change a
>
> > > lot and I need a way to update the config spec automatically.
> > > Prior to using Hudson,
> > > I have an automated process that will do this for me.  I think there
>
> > > should be an option in the ClearCase plugin to allow the user to use
>
> > > this view and and nothing else (don't create it, don't update it,
> > > don't do anything except use it).
> > >
> > > ~Jason
> > >
> > > --------------------------------------------------------------------
> > > - To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> > >
> > >
> >
> > --
> > View this message in context:
> > http://www.nabble.com/ClearCase-plugin-using-dynamic-views-tp14298247p
> > 14300596.html
> >
> > Sent from the Hudson users mailing list archive at Nabble.com.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
> > _____________________________________________________________________
> > This e-mail has been scanned for viruses by MCI's Internet Managed
> > Scanning Services - powered by MessageLabs. For further information
> > visit http://www.mci.com
> >
> >
> >
> > ***  PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS E_MAIL.  ***
> >
> > AXA and AllianceBernstein: Winner of 'Morningstar Fund Manager of the
> > Year
> > 2006 - Australia'.
> > **********************************************************************
> > ***********
> > Important Note
> > This email (including any attachments) contains information which is
> > confidential and may be subject to legal privilege.  If you are not
> > the intended recipient you must not use, distribute or copy this
> > email.  If you have received this email in error please notify the
> > sender immediately and delete this email. Any views expressed in this
> > email are not necessarily the views of AXA.   Thank you.
> > **********************************************************************
> > ************
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Re: Re: ClearCase plugin using dynamic views

mezlight
The snapshot is still stable...

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf
Of Erik Ramfelt
Sent: Thursday, December 13, 2007 10:42 AM
To: [hidden email]
Subject: Re: Re: ClearCase plugin using dynamic views

Yes, you are right. It will be changed in the next version. And thanks
for the help description!

But, can you create snapshot views with the version you are currently
using? I replace all "\r\n" with "\n" for both dynamic and snapshot
views, and would like to know that it didnt break.

thanks
//Erik

On Dec 13, 2007 3:22 PM, Messmer, Jason <[hidden email]> wrote:

> It worked...Thanks...
>
> On the another note, I would suggest to change "View drive" to "View
> root" to be cross platform compliant with the following help
> description from the ClearCase admin manual:
>
> "Every dynamic view on a host is displayed as a subdirectory of the
> host's view root directory.
> On computers running Linux(R) or the UNIX(R) system, the default view
> root directory is /view.
> On Windows(R) computers, the default view root directory is \\view,
> which is mapped by default to drive M."
>
> For Unix, the user would have to specified /view as the view root and
> M:\ for Windows if they are using the standard default ClearCase
> settings.  Unless the view root is specified, by default you could
> have these as the default settings.
>
> ~Jay
>
>
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf

> Of Erik Ramfelt
> Sent: Wednesday, December 12, 2007 5:32 PM
> To: [hidden email]
>
> Subject: Re: ClearCase plugin using dynamic views
>
> Ive committed a fix that will replace "\r\n" with "\n" in the config
> spec when running on unix. Iit will be available at
> http://hudson.ramfelt.se in 1 hour. If you have the chance, test it
> and let me know how it went.
>
>
> //Erik
>
> On Dec 12, 2007 11:00 PM,  <[hidden email]> wrote:
> > Windows adds ^M characters as spare characters for the carriage
> > return
>
> > character. You may have to strip these characters at the UNIX end.
> >
> > I found a good conversation for the same at the following link:
> >
> > http://lists.gnupg.org/pipermail/gnupg-users/2002-November/015809.ht
> > ml
> >
> > I hope this helps
> >
> >
> >
> >
> >              mezlight
> >              <Jason.Messmer@xe
> >              rox.com>
> To
> >                                        [hidden email]
> >              13/12/2007 05:15
> cc
> >              AM
> >
> Subject
> >                                        Re: ClearCase plugin using
> dynamic
> >              Please respond to         views
> >              [hidden email].
> >                  java.net
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > eramfelt wrote:
> > >
> > > On Dec 12, 2007 5:07 PM, mezlight <[hidden email]> wrote:
> > >>
> > >> It seems like the dynamic view is being updated with the config
> > >> spec identified within the ClearCase plugin configuration.  I
> > >> thought the concept was to use the existing dynamic view and not
> > >> update the config spec.  I live in a build world that the config
> > >> spec changes every other day
> > >> (interfaces)
> > >> and it would be nice to use the dynamic views config spec as is
> > >> (maybe
> > an
> > >> option to the plugin configuration).  That way the owner (a
> > >> common
> > >> user) of the view can modify the config spec and not the actual
> > >> hudson project every time there is a change.
> > >
> > >>Yes, the plugin sets the config spec of the dynamic view, and if
> > >>the
>
> > >>config spec of the job changes (or the config spec changes in the
> > >>view) it will update the config spec in the dynamic view. The only

> > >>difference for the plugin between a dynamic and a snapshot view is

> > >>that the plugin can not create dynamic views (and that it will not

> > >>do "cleartool update"). The idea was that the dynamic view should
> > >>be
>
> > >>governed by the plugin and its config spec. That way it was
> > >>simpler for our administrators to manage the dynamic views on
> > >>machines, in our test lab, and then rebuild using a different
config spec.
> > >>Perhaps this should be better described in the documentation.
> > >
> > >>I dont really understand your problem that the dynamic view is
> > >>updated with a new config spec. If someone needs to change the
> > >>config spec, then they could do it through Hudson and then
rebuild.
> > >>Or am I missing something here?
> > >
> > >>regards
> > >> //Erik
> > > Yeah I know it should be govern through Hudson but I was just
> > > thinking if I am using a dynamic view created prior to the project

> > > then it would be easier to update the view from the command line
> > > (I am always in that environment) then going through Hudson (which

> > > is simple enough).  The dilemma that I have is my config specs
> > > change a
>
> > > lot and I need a way to update the config spec automatically.
> > > Prior to using Hudson,
> > > I have an automated process that will do this for me.  I think
> > > there
>
> > > should be an option in the ClearCase plugin to allow the user to
> > > use
>
> > > this view and and nothing else (don't create it, don't update it,
> > > don't do anything except use it).
> > >
> > > ~Jason
> > >
> > > ------------------------------------------------------------------
> > > --
> > > - To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> > >
> > >
> >
> > --
> > View this message in context:
> > http://www.nabble.com/ClearCase-plugin-using-dynamic-views-tp1429824
> > 7p
> > 14300596.html
> >
> > Sent from the Hudson users mailing list archive at Nabble.com.
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
> > ____________________________________________________________________
> > _ This e-mail has been scanned for viruses by MCI's Internet Managed

> > Scanning Services - powered by MessageLabs. For further information
> > visit http://www.mci.com
> >
> >
> >
> > ***  PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS E_MAIL.  
> > ***
> >
> > AXA and AllianceBernstein: Winner of 'Morningstar Fund Manager of
> > the Year
> > 2006 - Australia'.
> > ********************************************************************
> > **
> > ***********
> > Important Note
> > This email (including any attachments) contains information which is

> > confidential and may be subject to legal privilege.  If you are not
> > the intended recipient you must not use, distribute or copy this
> > email.  If you have received this email in error please notify the
> > sender immediately and delete this email. Any views expressed in
this

> > email are not necessarily the views of AXA.   Thank you.
> > ********************************************************************
> > **
> > ************
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

ClearCase project setup issue

anubhav.berry
We have a project structure which represents the following:

1) Project A
2) Project B

Both these projects exist in 1 clearcase profile.

I want to maintain the same project structure that exists in my dev
environment. I do not want to follow the workspace path created by Hudson.

Is there any way that I could achieve this?

Thanks in advance

***  PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS E_MAIL.  ***

AXA and AllianceBernstein: Winner of 'Morningstar Fund Manager of the Year
2006 - Australia'.
*********************************************************************************
Important Note
This email (including any attachments) contains information which is
confidential and may be subject to legal privilege.  If you are not
the intended recipient you must not use, distribute or copy this
email.  If you have received this email in error please notify the
sender immediately and delete this email. Any views expressed in this
email are not necessarily the views of AXA.   Thank you.
**********************************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ClearCase project setup issue

Erik Ramfelt
On Dec 14, 2007 2:11 AM,  <[hidden email]> wrote:
> We have a project structure which represents the following:
>
> 1) Project A
> 2) Project B
>
> Both these projects exist in 1 clearcase profile.

With profile, do you mean a VOB? That is no problem, if you want to
have two jobs that reference only one project in the vob you can do so
in the config spec by "load \vob1\projectA"

> I want to maintain the same project structure that exists in my dev
> environment. I do not want to follow the workspace path created by Hudson.

How does your existing dev environment look like? Why do you not want
to check out to the workspace?

//Erik

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ClearCase project setup issue

anubhav.berry
Hi Erik,

Its not the loading that's the problem. It's the setup. The following is
the setup that we have in our DEV environment:

1) C:\ccviews\hudson_view\<project 1>
2) C:\ccviews\hudson_view\<project 2>
3) C:\ccviews\hudson_view\<project 3>

When I configure Hudson to load my projects, the hudson workspace looks
like the following:

1) usr/ccviews/hudson_server_view/jobs/<project 1>/workspace/<view_1_name>
2) usr/ccviews/hudson_server_view/jobs/<project 2>/workspace/<view_2_name>
3) usr/ccviews/hudson_server_view/jobs/<project 3>/workspace/<view_3_name>

I want to maintain the abovementioned directory (DEV environment) structure
instead of the one hudson creates. I know this seems impractical but this
is a requirement for our build environment.

Thanks



                                                                           
             "Erik Ramfelt"                                                
             <[hidden email]                                            
             om>                                                        To
             Sent by:                  [hidden email]          
             erik.ramfelt@gmai                                          cc
             l.com                                                        
                                                                   Subject
                                       Re: ClearCase project setup issue  
             14/12/2007 08:05                                              
             PM                                                            
                                                                           
                                                                           
             Please respond to                                            
             [hidden email].                                            
                 java.net                                                  
                                                                           
                                                                           




On Dec 14, 2007 2:11 AM,  <[hidden email]> wrote:
> We have a project structure which represents the following:
>
> 1) Project A
> 2) Project B
>
> Both these projects exist in 1 clearcase profile.

With profile, do you mean a VOB? That is no problem, if you want to
have two jobs that reference only one project in the vob you can do so
in the config spec by "load \vob1\projectA"

> I want to maintain the same project structure that exists in my dev
> environment. I do not want to follow the workspace path created by
Hudson.

How does your existing dev environment look like? Why do you not want
to check out to the workspace?

//Erik

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


_____________________________________________________________________
This e-mail has been scanned for viruses by MCI's Internet Managed
Scanning Services - powered by MessageLabs. For further information
visit http://www.mci.com



***  PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS E_MAIL.  ***

AXA and AllianceBernstein: Winner of 'Morningstar Fund Manager of the Year
2006 - Australia'.
*********************************************************************************
Important Note
This email (including any attachments) contains information which is
confidential and may be subject to legal privilege.  If you are not
the intended recipient you must not use, distribute or copy this
email.  If you have received this email in error please notify the
sender immediately and delete this email. Any views expressed in this
email are not necessarily the views of AXA.   Thank you.
**********************************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Loading...