Jump to content

Joerg Hampel

  • Content Count

  • Joined

  • Last visited

  • Days Won


Joerg Hampel last won the day on March 27

Joerg Hampel had the most liked content!

Community Reputation

21 Excellent

1 Follower

About Joerg Hampel

  • Birthday July 7

Contact Methods

  • Website URL
  • Skype

Profile Information

  • Gender
  • Location
  • Interests
    software development in teams

Recent Profile Visitors

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

  1. When adding contributors to VI Packages on vipm.io, the UI suggests that one can search for "vipm, github, and gitlab names": I tried that with one of my colleagues who is on GitLab but not on VIPM.io, but the search doesn't bring him up: Should this work?
  2. Hey JKI team, is it possible to programmatically update an existing .vipc (or, alternatively, create a new one) with a given .vip file? Our use is case is the following: After building a .vip automatically, we'd like to install it to the very system it was built on automatically. Seeing as we already have a tool to apply .vipc files through the VIPM API, and as we could use it "as-is" for this, we'd prefer to install the .vip this way. Thanks for the great tool, Jörg
  3. Jim, as always, your elaboration is spot on. Here's a screenshot of what our tools do: So other than the fact that we write all the build numbers in one go (the whole cluster), it's what you described above. Thanks for taking the suggestion into consideration.
  4. With VIPM 2020.3 (build 2540) and VIPM API 2020.0.2.73, it's not possible to supply a major number of 0 via the API, the API returns an error 42: Seeing as we also build projects that are in a pre-v1.0 state, I don't see a reason to not allow the major build number to be 0. I was actually tempted to file a bug report... 😉
  5. For one of our customer projects, upgrading from v1.0.2 to v1.1.0 resulted in an error when trying to build an executable from the project (downgrading to v1.0.2 fixed the build): I understand that we need to tidy our customer's project, having Caraya dependencies in the build is not what we want. The reason I'm posting here is that I'd be interested in understanding why this VI would break the build. Thanks, Joerg
  6. We use G-CLI to execute our CI tools, so we'd write back to G-CLI (and also to the front panel of the tool in case we run it manually). So the point would be to get the progress information back into the VI that's actually using the VIPM API. vipb.mov
  7. Building a VI package can take quite a while. For our Release Automation Tools, it takes about 20 minutes. Even though we build our packages on the build server now, it would be great to be able to feed back the progress of the build process to the CI system. As an example, the NI Application Builder API offers "progress bar" events, which you can register for and then show the progress details as you see fit: The VI Package Builder shows at least a few pieces of progress information in its status bar. Maybe these could be "routed" back to the VIPM API?
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.