Navigation

    Inedo Community Forums

    Forums

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    1. Home
    2. jharbison
    3. Topics
    J
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Topics created by jharbison

    • J

      Proper way to use $PSEval with boolean operations?
      Support • buildmaster powershell • • jharbison  

      2
      0
      Votes
      2
      Posts
      11
      Views

      jrasch

      The problem is that OtterScript attempts to parse those variables first. Just use quotes: set $foo = true; set $bar = true; set $foobar = $PSEval("$foo -and $bar"); Log-Information `$foobar = $foobar; # prints: $foobar = True
    • J

      Legacy Build Triggers
      Support • buildmaster • • jharbison  

      4
      0
      Votes
      4
      Posts
      26
      Views

      ?

      Just as a quick update, this was added to our roadmap as an item we will be including. It'll be implemented likely using the same mechanisms as the Repository Monitors, so it gives a lot more flexibility with regards to what it can do (create builds, create releases, etc), and also uses cron-syntax for scheduling so you have even more flexibility. No ETA, but I've added this post to the project plan so that we will upate it once it gets started.
    • J

      +1 for BM-3239
      Support • buildmaster • • jharbison  

      2
      0
      Votes
      2
      Posts
      5
      Views

      ?

      Thanks for the usecase - that's interesting and a good point in favor of doing this. Unfortunately after a brief review I've found that it's a little more technically complex than we first anticipated. I still think that we will do it, but it isn't something we can just drop in the next release.
    • J

      Are Package Notes Supported?
      Support • buildmaster packages triggered-builds • • jharbison  

      2
      0
      Votes
      2
      Posts
      7
      Views

      atripp

      Hi Josh, Sorry, this seems to be a v6 glitch! But we're on it :) I've submitted BM-3192 and then inedo-docs/#6 to update our documentation. Your understanding of how the feature is supposed to work is correct, and your use-case is how it's supposed to be. Thanks for reporting it !
    • J

      [Feature Request] Set-ReleaseVariable support all types
      Support • buildmaster variables • • jharbison  

      2
      0
      Votes
      2
      Posts
      6
      Views

      T

      Yes, here is the tracking issue: BM-3165
    • J

      Variables in Descriptions
      Support • buildmaster variables • • jharbison  

      2
      0
      Votes
      2
      Posts
      10
      Views

      ben

      Hello Josh, I agree that this would be very useful to have. I've filed IEE-8, which will allow the use of variables in block descriptions if the script contains ##AH:EvaluateStatementDescriptions at the top.
    • J

      Call Operation with Dynamic Options
      Support • buildmaster • • jharbison  

      4
      0
      Votes
      4
      Posts
      0
      Views

      ?

      This has been added as BM-3004, and is currently scheduled for 5.6.10.
    • J

      Variable as Lock Token
      Support • buildmaster variables • • jharbison  

      5
      0
      Votes
      5
      Posts
      11
      Views

      J

      That operation looks exactly like what I am trying to achieve. What is the behavior when all of the servers in the pool have been acquired? Does current execution wait or does an error get thrown?
    • J

      Retrieve All Release Variables for a Given Release
      Support • buildmaster variables releases • • jharbison  

      3
      0
      Votes
      3
      Posts
      8
      Views

      ?

      Don't use that, use the Variables API instead.
    • J

      Feature Request - Specify Release Template When Using Release API
      Support • buildmaster api templates • • jharbison  

      2
      0
      Votes
      2
      Posts
      7
      Views

      ?

      We'll add this, likely as a separate endpoint i.e. api/releases/create-from-template or something like that. It will appear as BM-2384 in the release notes (likely before it is actually documented on inedo.com).
    • J

      Raise Error Syntax
      Support • buildmaster error documentation example • • jharbison  

      3
      0
      Votes
      3
      Posts
      5
      Views

      ?

      That is exactly what I was looking for. Thank you.
    • J

      Release Template Package Variables Missing
      Support • buildmaster packages bug • • jharbison  

      4
      0
      Votes
      4
      Posts
      6
      Views

      ?

      Thanks for the clarification; I was able to repro this and logged a bug report (BM-2371). It will be addressed in a future maintence release.
    • J

      Recursive Variable Evaluation
      Support • buildmaster variables • • jharbison  

      4
      0
      Votes
      4
      Posts
      7
      Views

      ?

      We will implement this eventually once we have the specs nailed down. The plan is to offer a per-variable setting (in the same vein as the "sensitive" option) so it shouldn't break backwards compatibility.
    • J

      Execute-PowerShell Throws Exception
      Support • buildmaster powershell • • jharbison  

      3
      0
      Votes
      3
      Posts
      8
      Views

      ?

      Thanks. That was the problem. After updating the Windows extension from 5.5.0 to 5.6.0 the powershell command is working again.
    • J

      Exception Accessing MapItem
      Support • buildmaster variables • • jharbison  

      2
      0
      Votes
      2
      Posts
      7
      Views

      ?

      The way is correct, but it appears there's a bug in the evaluation while accessing the variable; this will be fixed in [BM-2278], which brought code in from Otter that fixes this bug.
    • J

      Inline PSExec Variable Evaluation
      Support • buildmaster variables • • jharbison  

      3
      0
      Votes
      3
      Posts
      15
      Views

      ?

      Thank you. The source code makes it explicitly clear what is going on. I was assuming that the OtterScript variables were being parsed out directly from the text input rather than being passed to the PSParser before hand. This also explains my troubles with the List and Map variable types as I was attempting to utilize them inline in my PSExec steps. I would suggest mentioning this parse behavior in the PSExec documentation link text and in the "Inline Script Execution" section of link text
    • J

      Parallel Loop Block
      Support • buildmaster workflows • • jharbison  

      2
      0
      Votes
      2
      Posts
      12
      Views

      ?

      Yes indeed, take a look at Asynchronous Blocks. Here is how you would do it in OtterScript: foreach $value in @list { with async { ... items ... } } await;
    • J

      Subversion "Get Latest Source" Error on Windows Inedo Agent
      Support • buildmaster agents subversion • • jharbison  

      6
      0
      Votes
      6
      Posts
      11
      Views

      ?

      Alright, v5.1.2 was released and it should be correct now :)
    • 1 / 1