You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Ben Popp <bp...@Endeca.com> on 2008/02/26 21:30:37 UTC

Password expiration

Hello - 

I'm using continuum 1.1 and my passwords just started to expire:
"Password will expire on Tue Feb 26 14:03:45 EST 2008."  

Is there any way to either disable password expiration, disable the
requirements to cycle passwords, or extend the timeout period for
expiration?

I looked through the config files and I found places to configure LDAP
but nowhere to configure the default account management behavior. 

Thanks,
Ben


RE: Access Continuum build number value?

Posted by "Tawfik, Sameh E" <Sa...@fairisaac.com>.
Hi Nico,

Thanks for your quick response, but could you give a little more
information about how to use ${basedir} to retrieve Continuum build
number? Is there is an example I can review?

In my parent Maven pom.xml, I've the following section:

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-jar-plugin</artifactId>
                <configuration>
                    <archive>
                        <manifestEntries>
                            <Built-By>XYZ, Inc.</Built-By>
                            <Module-version>1.0.0</Module-version>
                            <Build-number>3953</Build-number>
                            <Build-date>APR.11.2008</Build-date>
                            <Mode>development</Mode>
                        </manifestEntries>
                    </archive>
                </configuration>
            </plugin>

Currently, as shown above the build number value is hard coded, so my
goal is to automatically update the above build number value with
Continuum build number whenever Continuum runs a build. And also, the
build date if possible?

Can this be done?

  Thanks,
 
       Sameh

-----Original Message-----
From: Nicolas Loison [mailto:nicolas.loison1@gmail.com] 
Sent: Friday, April 11, 2008 1:13 PM
To: users@continuum.apache.org
Subject: Re: Access Continuum build number value?

Hello,

The ${basedir} variable allow you to know the build number information.

Nico

2008/4/11, Tawfik, Sameh E <Sa...@fairisaac.com>:
>
>
>
> During the build, I need to obtain the current build number value and
> pass it on to another process, so where does Continuum save the build
> number information? Is there is a file I can read to retrieve this
> information from?
>
> Every time, Continuum runs it increment the current build number value
> by one, so where does it retrieve this value from?
>
> Thanks,
>
>    Sameh
> This email and any files transmitted with it are confidential,
proprietary
> and intended solely for the individual or entity to whom they are
> addressed.
> If you have received this email in error please delete it immediately.
>
>
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.


Re: Access Continuum build number value?

Posted by Nicolas Loison <ni...@gmail.com>.
Hello,

The ${basedir} variable allow you to know the build number information.

Nico

2008/4/11, Tawfik, Sameh E <Sa...@fairisaac.com>:
>
>
>
> During the build, I need to obtain the current build number value and
> pass it on to another process, so where does Continuum save the build
> number information? Is there is a file I can read to retrieve this
> information from?
>
> Every time, Continuum runs it increment the current build number value
> by one, so where does it retrieve this value from?
>
> Thanks,
>
>    Sameh
> This email and any files transmitted with it are confidential, proprietary
> and intended solely for the individual or entity to whom they are
> addressed.
> If you have received this email in error please delete it immediately.
>
>

RE: Access Continuum build number value?

Posted by "Tawfik, Sameh E" <Sa...@fairisaac.com>.
Marin,

This is exactly what I needed, and it worked fine.

Just one more thing, is there is another property I can use for retrieving the value of the build date?

 Thanks,

   Sameh

-----Original Message-----
From: Martin Höller [mailto:martin@xss.co.at] 
Sent: Monday, April 14, 2008 2:37 AM
To: users@continuum.apache.org
Subject: Re: Access Continuum build number value?

On 11 Apr 2008, Tawfik, Sameh E wrote:

> 
> 
> During the build, I need to obtain the current build number value and
> pass it on to another process, so where does Continuum save the build
> number information? Is there is a file I can read to retrieve this
> information from?

Not a file, but a system property: continuum.project.nextBuild.number
See this thread for more information:
http://www.nabble.com/continuum.project.currentBuild.number-to16012461s177.html#a16012461

hth,
- martin

PS: Please start a new thread for new topics and don't reply to old
    messages.
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.


Re: Access Continuum build number value?

Posted by Martin Höller <ma...@xss.co.at>.
On 11 Apr 2008, Tawfik, Sameh E wrote:

> 
> 
> During the build, I need to obtain the current build number value and
> pass it on to another process, so where does Continuum save the build
> number information? Is there is a file I can read to retrieve this
> information from?

Not a file, but a system property: continuum.project.nextBuild.number
See this thread for more information:
http://www.nabble.com/continuum.project.currentBuild.number-to16012461s177.html#a16012461

hth,
- martin

PS: Please start a new thread for new topics and don't reply to old
    messages.

Access Continuum build number value?

Posted by "Tawfik, Sameh E" <Sa...@fairisaac.com>.

During the build, I need to obtain the current build number value and
pass it on to another process, so where does Continuum save the build
number information? Is there is a file I can read to retrieve this
information from?

Every time, Continuum runs it increment the current build number value
by one, so where does it retrieve this value from?

Thanks,

   Sameh
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.


Continuum email build message.

Posted by "Tawfik, Sameh E" <Sa...@fairisaac.com>.
Continuum does not report any SCM changes under the SCM heading, but
instead it reports the SCM changes under "Other Changes Since Last
Success" section?

When Continuum finishes a build and sends an email, the email body shows
the following:

************************************************************************
****
SCM Changes:
************************************************************************
****
No files changed

But when I click on the build link, and open the build results I see the
SCM changes are reported under other "Changes Since Last Success"
heading?

So, there are few issues here:

1. In Continuum email message it reports there are "No files changed"
under the " SCM Changes:" section which is not true.

2. The files that were changed with the authors comments are listed
under "Other Changes Since Last Success" section in the build history
report only?

For example the email body looks as follow:
************************************************************************
****
SCM Changes:
************************************************************************
****
No files changed

************************************************************************
****
Dependencies Changes:
************************************************************************
****
No dependencies changed


And the build results history report looks as follow:

SCM Changes
------------
No SCM changes
 
Other Changes Since Last Success
--------------------------------
Author Date Comment Files 
SamehTawfik 

How can we fix this situation?

 Thanks,

   Sameh
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.


ContinuumBuildExecutorException: Could not find Maven project descriptor?

Posted by "Tawfik, Sameh E" <Sa...@fairisaac.com>.

After Continuum finishes running a build, when I look at the build
history I found two outputs. The first one is marked with the build
error icon, and the second one is marked as successful. This happens
every time Continuum runs a build.

Does anyone know anything about this error?

The build error has the following error message:

Build Error
-----------
org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error
executing action 'update-project-from-working-directory' at
org.apache.maven.continuum.buildcontroller.DefaultBuildController.perfor
mAction(DefaultBuildController.java:434)at
org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(
DefaultBuildController.java:139)at
org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec
uteTask(BuildProjectTaskExecutor.java:50)at
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut
orRunnable$1.run(ThreadedTaskQueueExecutor.java:116)at
edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter
.call(Executors.java:442)at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask
.java:176)at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker
.runTask(ThreadPoolExecutor.java:665)at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker
.run(ThreadPoolExecutor.java:690)at
java.lang.Thread.run(Thread.java:619)

Caused by:
----------
org.apache.maven.continuum.execution.ContinuumBuildExecutorException:
Could not find Maven project descriptor. 

at
org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda
teProjectFromCheckOut(MavenTwoBuildExecutor.java:148) at
org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectory
ContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction
.java:75) at
org.apache.maven.continuum.buildcontroller.DefaultBuildController.perfor
mAction(DefaultBuildController.java:408)
	... 8 more
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.


Re: Password expiration

Posted by Wendy Smoak <ws...@gmail.com>.
On Fri, Feb 29, 2008 at 11:28 AM, Johnathan Gifford
<jg...@wernervas.com> wrote:
> <ws...@gmail.com> wrote:
>  > If you're running Continuum standalone, then you can put it in
>  > /path/to/continuum/conf/security.properties .
>
>  So the fact that this file doesn't currently exist means I need to create it with the values specified at this URL:
>
>  http://redback.codehaus.org/configuration.html

Yes, create it if it's not there.  You only need to add the properties
for which you want to override the default values.

-- 
Wendy

Re: Password expiration

Posted by Johnathan Gifford <jg...@wernervas.com>.
>>> On Fri, Feb 29, 2008 at 12:22 PM, in message
<ad...@mail.gmail.com>, "Wendy Smoak"
<ws...@gmail.com> wrote: 
> If you're running Continuum standalone, then you can put it in
> /path/to/continuum/conf/security.properties .

So the fact that this file doesn't currently exist means I need to create it with the values specified at this URL:

http://redback.codehaus.org/configuration.html

Correct?

Thanks,

Johnathan



Re: Password expiration

Posted by Wendy Smoak <ws...@gmail.com>.
On Fri, Feb 29, 2008 at 11:18 AM, Johnathan Gifford
<jg...@wernervas.com> wrote:
> Hmm... I've now ran into this issue.  I changed the password(s) for the accounts I have, but Continuum keeps
> indicating 'Account Locked'.  Where is this security.properties file suppose to be placed for Continuum and
> what path/file am I supposed to enable this in.

If you're running Continuum standalone, then you can put it in
/path/to/continuum/conf/security.properties .

Editing that file isn't going to fix a locked account though.  If it's
the admin account, stopping and re-starting Continuum should unlock
it.  If it's any other account, log in as a user administrator, edit
the account, and unlock it by un-checking the checkbox.

-- 
Wendy

Re: Password expiration

Posted by Johnathan Gifford <jg...@wernervas.com>.
Hmm... I've now ran into this issue.  I changed the password(s) for the accounts I have, but Continuum keeps indicating 'Account Locked'.  Where is this security.properties file suppose to be placed for Continuum and what path/file am I supposed to enable this in.

Johnathan

>>> On Tue, Feb 26, 2008 at  2:39 PM, in message
<ad...@mail.gmail.com>, "Wendy Smoak"
<ws...@gmail.com> wrote: 
> On Tue, Feb 26, 2008 at 1:30 PM, Ben Popp <bp...@endeca.com> wrote:
> 
>>  I'm using continuum 1.1 and my passwords just started to expire:
>>  "Password will expire on Tue Feb 26 14:03:45 EST 2008."
>>
>>  Is there any way to either disable password expiration, disable the
>>  requirements to cycle passwords, or extend the timeout period for
>>  expiration?
> 
> In security.properties, you can change these values:
> 
> security.policy.password.expiration.enabled=true
> security.policy.password.expiration.days=90
> 
> This should help:  http://redback.codehaus.org/configuration.html



Re: Password expiration

Posted by Wendy Smoak <ws...@gmail.com>.
On Tue, Feb 26, 2008 at 1:30 PM, Ben Popp <bp...@endeca.com> wrote:

>  I'm using continuum 1.1 and my passwords just started to expire:
>  "Password will expire on Tue Feb 26 14:03:45 EST 2008."
>
>  Is there any way to either disable password expiration, disable the
>  requirements to cycle passwords, or extend the timeout period for
>  expiration?

In security.properties, you can change these values:

security.policy.password.expiration.enabled=true
security.policy.password.expiration.days=90

This should help:  http://redback.codehaus.org/configuration.html

-- 
Wendy