Jump to content

Search the Community

Showing results for tags 'triggers'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Plastic SCM
    • General
    • Installation and configuration
    • Unity 3D
    • Unreal Engine
    • Plastic SCM on Mac
    • Plastic SCM on Linux
    • Gluon
    • Git interop
    • Integrations
    • Community Edition
    • Branching and merging
    • Announcements
  • Plastic SCM 4.0 Beta (Closed)
  • Plastic Cloud
    • General
    • Configuration
  • SemanticMerge
    • General
    • License
    • SCM's configuration
    • Share your experience!
    • External Parsers
  • GitJungle
  • Method History for Subversion
  • PlasticX Early Adopter Program's General Feedback
  • PlasticX Early Adopter Program's Issue Reporting
  • PlasticX Early Adopter Program's Feature Requests
  • PlasticX Early Adopter Program's Announcements

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 6 results

  1. Are proper cloud triggers still not supported? I want to set up adding attributes to branches on creation per this article https://blog.plasticscm.com/2019/06/archive-branches-in-plastic-scm.html
  2. Hi all! We are using after-checkin triggers to deploy builds via Jenkins when changes are made in certain branches. We have this working for a child branch of /main, but now we want to implement it for the /main branch itself. The issue is, when using br:/main as a filter, the trigger will fire for every child branch of /main when we only want it for changes in /main branch. Is there a way to let it filter for an exact branch name match rather than filtering for if the branch name contains the filter? Cheers!
  3. Hi, Let assume the same server trigger is fired twice in a raw, from two different sources (example: two checkin at the same time) Does the triggered script run twice in parallel, as two separate instances or there is a guarantee that the second trigger will start to run only after the first one is finished? Don't know if its matter, the server run on Linux. Regards, Ofir
  4. Hello, My team is working in a mixed OS X and Windows environment. We want the triggers we make to work on both systems, but I suspect our problem is that the paths we're using aren't valid for both operating systems. $ cm listtriggers 2 Update art on update ruby /Users/atlantisremixed/.arx-plastic/update_art.rb LoganBarnett after-update The Ruby script we're running works great for both OS X and Windows when running standalone, but that path won't work for WIndows in the trigger so it doesn't even get to the Ruby script. What can I do to make my trigger platform agnostic? All of the examples in the PDF seem to prefer one platform or another, but never something universal. It would be nice if I could just do ~ for a home directory but I don't think that expands correctly. Perhaps I was doing that wrong? Thanks in advance! -Logan
  5. Hi, I'm trying to set up an after-setselector trigger to run using a powershell script. And, I'm having trouble accessing the "environment variables". I've added the following to server.conf: <TriggerVariables> <TriggerVariable name="SERVER_TRIGGERS_PATH" value="c:\triggers\server" /> <TriggerVariable name="TRIGGERS_PATH" value="c:\triggers" /> </TriggerVariables> and I've added the following to client.conf: <TriggerVariables> <TriggerVariable name="CLIENT_TRIGGERS_PATH" value="c:\triggers\client" /> </TriggerVariables> In my powershell script I'm just trying to access the variables (based on what is in the trigger guide) and then printing them out by doing the following: [string] $spacePath = $Env:PLASTIC_WORKSPACE_PATH; [string] $spaceName = $Env:PLASTIC_WORKSPACE_NAME; [string] $wkspacePATH = $Env:WKSPACE_PATH; [string] $serverTrigger = $Env:SERVER_TRIGGERS_PATH; [string] $clientTrigger = $Env:CLIENT_TRIGGERS_PATH; [string] $triggerPath = $Env:TRIGGERS_PATH; [string] $plasticUser = $Env:PLASTIC_USER; [string] $plasticClientMachine = $Env:PLASTIC_CLIENTMACHINE; [string] $plasticPlasticServer = $Env:PLASTIC_SERVER; Add-Content $outputLocation "spacePath: $spacePath"; Add-Content $outputLocation "spaceName: $spaceName"; Add-Content $outputLocation "wkspacePATH: $wkspacePATH"; Add-Content $outputLocation "serverTrigger: $serverTrigger"; Add-Content $outputLocation "clientTrigger: $clientTrigger"; Add-Content $outputLocation "triggerPath: $triggerPath"; Add-Content $outputLocation "plasticUser: $plasticUser"; Add-Content $outputLocation "plasticPlasticServer: $plasticPlasticServer"; Add-Content $outputLocation "plasticClientMachine: $plasticClientMachine"; And in the output location this is what is returned: spacePath: c:\plastic\tests\triggers spaceName: Plastic.Tests wkspacePATH: serverTrigger: clientTrigger: triggerPath: plasticUser: misterhux plasticPlasticServer: localhost:8087 plasticClientMachine: 08THORP5520 So my question is, am I doing something wrong or does the trigger mechanism not actually set environment variables? Thank you.
  6. \We're doing some testing, and I'm trying to run the following trigger, to make Plastic run a basic .bat file when any commit is made in Plastic. The .bat file (for now) just creates a text file letting us know the trigger works. I placed the .bat file on the Plastic Server, and had a user make a commit at their local machine. But it doesn't appear to run the .bat file, because the .txt file it SHOULD create, doesn't get created. cm maketrigger after-checkin "Alert Buildbot" "C:\Plastic_Commit_Triggers\Buildbot_Trigger.bat" --server=disti-plastic-1:8087 --filter="rep:M1A2S_VMT,*" We've ran the .bat file on its own and it does create the .txt file when you run it. But Plastic doesn't seem to run it. Any suggestions, or am I possibly doing it wrong? The .bat file literally only runs the following command: SET > %TEMP%\SET.TXT TEMP is set in environment variables to look in the following location: %USERPROFILE%\AppData\Local\Temp Which should create the "set.txt" file that lists the environment variables, in the following location: C:\Users\ralley\AppData\Local\Temp\2 What am I missing?
×
×
  • Create New...