Yeah, just semantics. Like you can't know the parameters "name" or
anything like that in the script itself, or do things like "iterate on all
parameter names" - you can only know their injected *value*, so if you want
to make logic depend on a parameter's name, you have to assign it to a
local
Hi folks - unfortunately a problem sneaked through our automated regression
in 23.2.0 which prevents UI navigation via Stage History to older stage
runs in the history when you're already viewing the detail of an individual
stage (Stage Details view).
You can still navigate to these as normal
yes- i'm aware that parameters are replaced before the script is written
into the agent and executed.
while it's correct that scripts don't know where the information inside
them comes from, this is true for any script not just ones used by gocd.
perhaps these are more semantic level points.
eg i
On Mon, Jul 24, 2023 at 10:44 AM Chad Wilson wrote:
> On Mon, Jul 24, 2023 at 8:44 PM Joshua Franta wrote:
>
>>
>> chad thanks for your answer.
>>
>> i think the main source of confusion is that I thought parameters could
>> only be referred to in scripts!
>> I didn't know you could refer to
If you read Jason's message a bit more closely he is conveying that the
script's runtime environment has no knowledge of the parameters - not that
they can't be used at all.
They are just tokens that have already been 'realized' or replaced into the
content by the time the script/task runs. So
Jason, your knowledge here is off. Parameters can be used in scripts, see a
previous email I this thread that shows how it works.
On Mon, Jul 24, 2023, 4:11 PM Jason Smyth wrote:
> Hi Josh,
>
> I think there may be some confusion here regarding GoCD terminology and
> common concepts.
>
> > i
Hi Josh,
I think there may be some confusion here regarding GoCD terminology and
common concepts.
> i think the main source of confusion is that I thought parameters could
only be referred to in scripts!
> I didn't know you could refer to them inside of other configuration
properties!
To the
On Mon, Jul 24, 2023 at 8:44 PM Joshua Franta wrote:
>
> chad thanks for your answer.
>
> i think the main source of confusion is that I thought parameters could
> only be referred to in scripts!
> I didn't know you could refer to them inside of other configuration
> properties!
> Is this
On Mon, Jul 24, 2023 at 8:44 PM Joshua Franta wrote:
>
> chad thanks for your answer.
>
> i think the main source of confusion is that I thought parameters could
> only be referred to in scripts!
> I didn't know you could refer to them inside of other configuration
> properties!
> Is this
chad thanks for your answer.
i think the main source of confusion is that I thought parameters could
only be referred to in scripts!
I didn't know you could refer to them inside of other configuration
properties!
Is this documented? Regardless that's super useful, there's probably some
other
10 matches
Mail list logo
