Jump to content

Mikael Kalms

Members
  • Content Count

    100
  • Joined

  • Last visited

  • Days Won

    10

Mikael Kalms last won the day on March 17 2017

Mikael Kalms had the most liked content!

Community Reputation

1 Neutral

About Mikael Kalms

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. There is also ... this solution: https://github.com/Kalmalyzer/MuteThoseBloodyOwls
  2. Storing owl data on the server assumes that one human = one account on one server. You are reasonably close to that with a centralized workflow where users work directly against Plastic Cloud. We also have accounts which are for a particular purpose (example: build system) rather than a particular human. The mapping is not accurate in those cases. I'm not sure how important those accounts are in the grand scheme of things. I suspect it will be more difficult for you in distributed scenarios involving on-premise servers: Which server will a user's owl information be stored on? I'm going to make a comparison here, between the Unreal Editor and Plastic. Like Plastic, the Unreal Editor has a couple of short tutorials, that are situational (tutorial X becomes available when entering page X). 4 out of 4 developers I have asked in the office, would like to mute all the owls in their Plastic clients right now. 0 out of 4 developers I have asked in the office, would like to mute all the tutorials in their Unreal Editors right now. The main problem that these developers have is that the owls in Plastic are intrusive, while the tutorial indicator in Unreal Editor is not intrusive. The developers here would have been OK with the owls if they had been less in-your-face. They steal a lot of screen real-estate and interrupt your train of thought when they appear. That is why people here are annoyed with them. I did not ask for this owl to appear. This is intrusive: I did not ask for the tutorial indicator to appear on first application launch. This is slightly intrusive, but I only need to click away the "welcome" popup once: I did not ask for the tutorial indicator to appear on subsequent pages either. This is not intrusive:
  3. I'm aware of the "Got it, don't show me again" button. I made this post because I had grown tired of muting the messages one-by-one. My personal frustration comes from the owl system not realizing that me (one human) is using Plastic on multiple machines. When I'm updating to an Owl-enabled Plastic version on my third computer, I am not interested in reading any of the owl popups on that computer because I have already been through these once on the other two machines. I have no hard data on which owls appear unwanted to the team here. I'll let you know if I can pinpoint any that cause frustration with my colleagues.
  4. I'm aware of the "Got it, don't show me again" button. I made this post because I had grown tired of muting the messages one-by-one. My personal frustration comes from the owl system not realizing that me (one human) is using Plastic on multiple machines. When I'm updating to an Owl-enabled Plastic version on my third computer, I am not interested in reading any of the owl popups on that computer because I have already been through these once on the other two machines. I have no hard data on which owls appear unwanted to the team here. I'll let you know if I can pinpoint any that cause frustration with my colleagues.
  5. Hi, I'm using Plastic on several machines in parallel. I'm getting tired of muting all the *** owls on all machines. How do I do it? Don't get me wrong, the owls seem like a great feature for people getting started with Plastic, but some people who are experienced with Plastic since before just want them gone. Several people on my team have asked me how to mute them all in one go, and I have no good answer. Mikael
  6. Hi, I have recently created two new Jenkins build jobs based off of an existing build job. The existing build job has been working fine for some time, but the two new build jobs fail. What I find is that with the new build jobs, I get the following error: groovy.lang.MissingPropertyException: No such property: PLASTICSCM_CHANGESET_ID for class: groovy.lang.Binding This is strange, and it is causing trouble when we are about to make a major release. I have a workaround, which I will use for the time being -- directly calling `cm status` and using that result instead of he PLASTICSCM_CHANGESET_ID variable. Still, it would be nice if you could find a solution for this long term. The entire project exists in a Plastic repo. The Jenkins build job is a Declarative Pipeline job. The Jenkinsfile is configured to be fetched as "Pipeline script from SCM", with a selector like this: repository "Freedom@FallDamage@Cloud" path "/" smartbranch "/main" (Use update is enabled, Lightweight checkout is enabled) I am not performing any extra checkouts, just relying on what Jenkins automatically does. Now, the step that fails looks like this: // Build 64-bit Windows Standalone player, with Steam activated // Source project location: ${SOURCE_DIR} // Target build location: ${SOURCE_DIR}/SteamBuild/input // Target executable name: ${PROJECT_NAME}.exe stage('Build') { steps { timeout(time: "${BUILD_STAGE_TIMEOUT_MINUTES}" as int, unit: 'MINUTES') { script { failedStage = STAGE_NAME try { bat "if exist ${WORKSPACE}\\UnityEditor.log del ${WORKSPACE}\\UnityEditor.log" bat "START /WAIT \"Unity\" \"${UNITY_INSTALLATION_DIR}/Editor/Unity.exe\"" + " -quit" + " -batchmode" + " -executeMethod CustomBuild.GenerateBuild_CommandLine" + " -BuildInfo.SourceControl.RepositoryServer \"<org>@Cloud\"" + " -BuildInfo.SourceControl.Repository \"${SCM_REPOSITORY_NAME}\"" + " -BuildInfo.SourceControl.ChangeSetId \"${PLASTICSCM_CHANGESET_ID}\"" + " -BuildInfo.BuildJob.Name \"${JOB_NAME}\"" + " -BuildInfo.BuildJob.Id \"#${BUILD_ID}\"" + " -BuildInfo.Configuration \"${CONFIGURATION}\"" + " -BuildInfo.BuildTimeStamp \"${BUILD_TIMESTAMP}\"" + " -CustomBuild.OnlineVersion \"${JOB_NAME}.${PLASTICSCM_CHANGESET_ID}\"" + " -CustomBuild.Configuration \"${CONFIGURATION}\"" + " -CustomBuild.TargetExecutable \"${SOURCE_DIR}/SteamBuild/input/${PROJECT_NAME}.exe\"" + " -projectPath \"${SOURCE_DIR}\"" + " -logFile \"${WORKSPACE}/UnityEditor.log\"" + " && IF ERRORLEVEL 1 EXIT /B 1" } finally { bat "type \"${WORKSPACE}\\UnityEditor.log\"" } } } } } It is the ${PLASTICSCM_CHANGESET_ID} variable reference which Jenkins claims is unassigned. Now, again -- I am using the same exact script, but with 4 environment variables changed, for another build job that is working well. This is what the Stage view looks like. I triggered the build job twice. The first time, the checkout took a long time since it had to pull down the entire repository. The second time, there were no changes to the repo, so checkout was quick. My wild guess: The PlasticSCM plugin does not publish changes or set some environment variables to Jenkins for a particular build job, until that job has run successfully at least once. Let me know if you want a support ticket with more detailed logs, build scripts & screenshots.
×
×
  • Create New...