Hi Aravind,
Thanks for the reply. Actually, I think there actually wasn't a problem,
just a misunderstanding on my part, followed by a log message that seemed
like failure, but maybe was just informational.
My confusion stems from how the Label for a pipeline is specified.
If I have 2 SVN materials in my pipeline, say 'A', and 'B', what I really
want to be able to specify for the label is 'MAX(A, B)', but instead I can
only choose ${A} or ${B} (or, perhaps, ${A}-${B}, but that doesn't scale
well to N materials).
For example, if I specify the label as '${A}', and then user commits new
code to material B, then the pipeline will trigger, but the label will be
unchanged, making it non-obvious that a new build has taken place.
Do you have a suggestion/solution/workaround for this?
Thanks,
-Eric.
On Fri, Apr 27, 2018 at 9:55 AM, Aravind SV <[email protected]> wrote:
> Hey Eric,
>
> I wonder if the user that the GoCD server is running as doesn't have the
> credentials to access the SVN repo. Maybe try to run the svn command as the
> user that the GoCD server is running as?
>
> Or, maybe you can change the user that the GoCD server is running as to
> your local user and verify? If you do that, you might need to change the
> permissions of C:\Program Files (x86)\Go Server (and all its children) to
> be your local user.
>
> Cheers,
> Aravind
>
>
> On Wed, Apr 25, 2018 at 8:56 PM, Eric Brandt <[email protected]>
> wrote:
>
>> Hello friends,
>>
>> I'm a new user, getting GoCD set up for the first time, migrating from
>> CC.NET. There are lots of things to like, but I'm having an issue that
>> has brought progress to a halt:
>>
>> It seems that my server will not update any of my SVN Materials.
>>
>> The Go Server log file fills lines like:
>>
>> 2018-04-25 02:20:47,331 WARN [materialUpdateThread]
>> MaterialUpdateService:181 - [Material Update] Skipping update of material
>> SvnMaterial{url=http://myrepository/folder, userName='my_username',
>> checkExternals=true} which has been in-progress since Tue Apr 24 13:24:42
>> EDT 2018
>>
>> There is typically a new line like this for each material in each of my
>> pipelines every 3 minutes.
>>
>> And then sometimes, (maybe related, maybe unrelated?) if I cancel a
>> pipeline that is in progress, the pipeline has its 'Trigger' and 'Trigger
>> With Options' buttons disabled, even though the pipeline is not Paused. At
>> that point, I have no way to start that pipeline without stopping and
>> restarting the Go Server service.
>>
>> I tried configuring the server logging to include additional logging for
>> SVN with the line:
>> <logger name="com.thoughtworks.go.domain.materials.svn" level="DEBUG"
>> />
>> added to logback-include.xml in the C:\program files (x86)\Go
>> Server\config dir, but I am not seeing any additional SVN-related log
>> messages.
>>
>> I can access the svn server from a command line interface (svn.exe) from
>> the machine running Go Server without a problem.
>>
>> I have googled for this problem, and haven't really found much.
>>
>> Can anyone suggest what to try next to troubleshoot this issue? It truly
>> is a stopping point for using GoCD, because polling never triggers a new
>> build, and manually forcing a build does not retrieve the latest SVN
>> revisions.
>>
>> Thanks in advance,
>> -Eric.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "go-cd" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.