Is it possible to publish a link to a release-artifact on a "github pages" page? This is easy like:
https://github.com/rocket-monkey/my-app/releases/download/v0.0.1/my-app.io-0.0.1.dmg
But, what it it's a private repository?
One workaround to to dedicate a public empty repository, in which you create dummy commits, one per release, with tags representing your "release", and where you can re-upload your artifacts initially published in your private repository.
That way, you can point interested parties to the public repository artifact release, instead of the private one.
Related
I created a repository (without link to git) for Google Dataform and a workspace.
I initialized a first setup and pushed those first files.
Where can I see the repo and all the commits I do in there?
Looked in Cloud Storage, Artifact Registry, Cloud Source Repositories but can't find it.
Dataform does not have all the functionality of Git so without linking to Github you won’t be able to see the repository. For your requirement, you can create Dataform repositories (Git repositories containing Dataform code, essentially) and create code workspaces attached to those repositories. Edit code in those workspaces, push the results to the relevant Git repository. You can also compile the repository/workspace Dataform code to Directed Acyclic Graphs (DAGs) of executable SQL and can also execute the compiled DAGs against BigQuery.
The repositories are listed here, please see the official documentation for more context.
You may also explore the possibility of connecting to a remote repository, as the Dataform repository doesn't meet your requirement for viewing commits.
I'd like to ask, how may I do a migration of mappings, worklets and workflows from Informatica PowerCenter Integ, to Prod.
Integ Enviroment and Prod are in different servers, so I can't just mouve folder from folder.
Is it possible? I can't find any refernece or tutorial.
Thank you in advance.
In Powercenter, its possible to copy form one env to another. Request everyone to check in their objects first adn log off from both source and target repo.
Open Repository Manager, connect to the source repository and select the folder you want to copy.
Click Edit > Copy.
Connect to the target repository. Connect to the target repository with the same user account used to connect to the source repository. If you do not have same user you need to use deployment group/deployment folder.
In the Navigator, select the target repository, and click Edit > Paste. You will get many options like - replacing objects, use latest version, check out etc. You can follow below link to get help.
https://docs.informatica.com/data-integration/powercenter/10-5/repository-guide/copying-folders-and-deployment-groups/copying-or-replacing-a-folder/steps-to-copy-or-replace-a-folder.html
Now, my preference would be to use deployment group or deployment folder. Its easy to use and easy to control - like if you want to replace 10 objects out of 100s, or you want to create a standard process for future migrations, or deploy using command task automatically, you can do as well.
I really liked the feature GitHub Template Repository where according to the documentation
After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files.
What I also want to accomplish is to copy the the labels and settings of the template repository. This would ease processes and bring in standardisation.
Following could be the possible settings which I would like to be inherited from template repository
Disable Allow merge commits
Rule of master branch i.e. Protected branches
GitHub pages source should be master branch /docs folder
Activate After pull requests are merged, you can have head branches deleted automatically
Have you tried this ? If yes, how were you able to do it ?
2020: For now, "Creating a repository from a template" does not extends to settings, only repository structure.
If said repository is part of an organization, you have a common set of settings you (as administrator of that organization) can manage.
Note: Jorge Leitao adds in the comments:
As of today (Jan. 2023) org-level settings do not support branch rules nor most of project settings (even Enterprise Plan)
I would like to run WSO2 on two hosts, one serves as manager and the other as gateway worker.
I consulted the clustering guide and product profiles documentation, and I understand that after configuring the two hosts correctly, I can run the product with selected profile:
-Dprofile=gateway-manager on the manager node
-Dprofile=gateway-worker on the gateway worker node
In addition to perform selective-run, I would also like the gateway-worker to have the minimal possible deployment, i.e. to be installed only with artifacts it really needs.
Three options I can think of, from best to worst:
Download a minimized deployment package - in case there is one? In the site I saw only complete package which contains artifacts of all the components. Are there other download options which contain selective artifacts per profile?
Download the complete package and then remove the artifacts which are not necessary for gateway-worker (how do I know which files/directories to remove?)
Download the source from github and run a selective build? (which components should I build and how do I package them for deployment)?
There are no separate product packs for each profiles to download. So option 1 is not there. But you can do the option 2 to some extent. You can remove the publisher, store and admin-dashboard application from the product by removing 'jaggeryapps' folder in 'wso2am-1.10.0/repository/deployment/server/' location. Other than that we are not recommending to remove any components from the pack.
You can check the profile generation code for API Manager 1.10 in here. It only has module import definitions. These component are needed to be there for each profile.
I need to use the mongo-storm library and Clojars doesn't have it. So I cloned the project, compiled and copied the jar to my lib folder by hand. But it is a team project and it is unacceptable for every member to do those steps by hand.
Are there any better and standard ideas on how to solve this issue?
Your team should have a private repository for this purpose. S3 is an ideal substrate for this, and you can use the s3-wagon-private Leiningen plugin to deploy and consume artifacts to/from a secured S3 bucket:
https://github.com/technomancy/s3-wagon-private
If the project has a license that allows it (if it's open source) you are allowed to push your own unofficial version to Clojars yourself using your own group ID. Clojars reserves the "org.clojars.username" group IDs for this purpose. This is described in https://github.com/ato/clojars-web/wiki/tutorial and https://github.com/technomancy/leiningen/blob/master/doc/DEPLOY.md .
The best way would probably be if you could contact the author and to urge him/her to do a proper release. (Also, the readme doesn't tell what license the project has.)
A solution that doesn't require setting up a private repository would be to leverage the checkouts capability in leiningen.
Ideally, if your team is using a maven based dependency management system (like Leiningen), you would have a repository manager set up. You can then deploy the library to your team's repository manager.
Most repository managers have Maven Central already included and make it easy to both add additional repositories to proxy (e.g. Clojars) and host your own repositories (for mongo-storm and the project being developed).
After getting one set up, one of the things you'll want to make sure your team does is either set as a repository proxy or as an additional repository to pull jars from.
You can find a list of repository managers on the maven site.