GitLab issueshttps://gitlab.com/gitlab-org/gitlab/-/issues2020-07-30T18:53:29Zhttps://gitlab.com/gitlab-org/gitlab/-/issues/227973Emoji is squished when used in tables2020-07-30T18:53:29ZSamirEmoji is squished when used in tables### Summary
When an emoji is used in a html table it may not render properly and be squished to below it's natural 20px width.
### Steps to reproduce
1. Go to a page with an `:emoji:` in a html table, any MR with a Danger comment wil...### Summary
When an emoji is used in a html table it may not render properly and be squished to below it's natural 20px width.
### Steps to reproduce
1. Go to a page with an `:emoji:` in a html table, any MR with a Danger comment will do.
* also reproduced in this very ticket below (so meta)
1. Reduce width of browser
1. See emoji being being squished
I believe this is only an issue when the image fallback renderer is being used. I could reproduce it on Chromium and two QtWebEngine browsers, but not on Firefox. I can only reproduce it on my Linux machine, I've tried a Mac and Google Chrome is fine there.
### Example Project
Any which use Danger. Other scenarios may arise where this happens too.
### What is the current *bug* behavior?
```markdown
<table>
<thead>
<tr>
<th width="5%"></th>
<th width="95%">
Heading 2
</th>
</tr>
</thead>
<tbody>
<tr>
<td>:warning:</td>
<td>Reducing width of the browser will squish the :warning: on the left.</td>
</tr>
</tbody>
</table>
```
This markdown is rendered as:
<table>
<thead>
<tr>
<th width="5%"></th>
<th width="95%">
Heading 2
</th>
</tr>
</thead>
<tbody>
<tr>
<td>:warning:</td>
<td>Reducing width of the browser will squish the :warning: on the left.</td>
</tr>
</tbody>
</table>
### What is the expected *correct* behavior?
The emoji should have it's normal width, even if used in this context.
### Output of checks
This bug happens on GitLab.com
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
Using the web inspector to set the `width: 20px` of `gl-emoji` seem to fix the issue. This change would need to be done somewhere in [emojis.scss](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/assets/stylesheets/framework/emojis.scss) I assume.
Original report on Danger issue tracker: https://github.com/danger/danger/issues/1243https://gitlab.com/gitlab-org/gitlab/-/issues/227875Feedback issue: Add additional Dependency Scanning Package Manager Support2023-04-21T19:18:51ZNicole SchwartzFeedback issue: Add additional Dependency Scanning Package Manager SupportHello!
This is a feedback issue designed to aggregate requests for additional supported package managers, versions, etc.
After commenting please š this issue!
Please indicate the following in your comment:
- language & version
- packa...Hello!
This is a feedback issue designed to aggregate requests for additional supported package managers, versions, etc.
After commenting please š this issue!
Please indicate the following in your comment:
- language & version
- package manager and version
- Self hosted or software as a service (GitLab dot com)
- how many users you have in your project
If it's a older version (older than one year or end of life/EOL) please be explicit around why you can't update at this time and what your estimate update schedule is (for example do you usually lag one year behind due to compliance proceses at your company taking that long).Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/227344Gitlab is throwing 404 for an existing project. Please help.2020-07-09T09:43:04ZAbhineet SharmaGitlab is throwing 404 for an existing project. Please help.GitLab has moved to a single codebase for GitLab CE and GitLab EE.
Please do not create issues here, instead create them at https://gitlab.com/gitlab-org/gitlab/issues.GitLab has moved to a single codebase for GitLab CE and GitLab EE.
Please do not create issues here, instead create them at https://gitlab.com/gitlab-org/gitlab/issues.https://gitlab.com/gitlab-org/gitlab/-/issues/226921Icon for MATLAB .m files in repository tree is not appropriate2023-10-24T02:06:07ZWill HirschIcon for MATLAB .m files in repository tree is not appropriate### Summary
MATLAB source files with .m extension appear in the repository tree with a "letter C" icon that is also used for .c files written in C. These icons seem to be a relatively recent addition via !28112. This is despite the feat...### Summary
MATLAB source files with .m extension appear in the repository tree with a "letter C" icon that is also used for .c files written in C. These icons seem to be a relatively recent addition via !28112. This is despite the feature that displays the composition of languages used in a repository successfully recognising the presence of lots of MATLAB code and no C code when this is the true composition of the repository.
### Steps to reproduce
1. Add a .m file written using MATLAB syntax to a repository
2. Browse to a list of repository files where the added file is visible.
### Example Project
See for example the project root for https://gitlab.com/tensors/tensor_toolbox (the most-starred MATLAB project on GitLab.com) which contains several .m files.
### What is the current *bug* behavior?
The icon used is a "C"
### What is the expected *correct* behavior?
A MATLAB-specific icon, M-related icon or generic file icon should be used.Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/225911Import Export Button - Is it missing or don't I know where it is?2023-04-26T17:19:40ZTim MurnaghanImport Export Button - Is it missing or don't I know where it is?<!--
* Use this issue template for suggesting new docs or updates to existing docs.
Note: Doc work as part of feature development is covered in the Feature Request template.
* For issues related to features of the docs.gitlab.com sit...<!--
* Use this issue template for suggesting new docs or updates to existing docs.
Note: Doc work as part of feature development is covered in the Feature Request template.
* For issues related to features of the docs.gitlab.com site, see
https://gitlab.com/gitlab-org/gitlab-docs/issues/
* For information about documentation content and process, see
https://docs.gitlab.com/ee/development/documentation/ -->
### Problem to solve
I've been invited to a project and need to copy it.
I have no idea if it's exportable - and export is a rare enough operation so I don't know where the button might be.
So documentation telling me that I might see a button (but not telling me where) depending on someone else's setting just isn't very helpful.
### Further details
<!--
* Any concepts, procedures, reference info we could add to make it easier to successfully use GitLab?
* Include use cases, benefits, and/or goals for this work.
* If adding content: What audience is it intended for? (What roles and scenarios?)
For ideas, see personas at https://design.gitlab.com/research/personas or the persona labels at
https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A
-->
### Proposal
~~Minimal change:~~
~~* Update the Export CTA color to `btn-warning-primary`~~
~~* :eyes: **[View prototype](https://www.figma.com/proto/QXMLNTLFYrq2Va1b973jga/Untitled?node-id=4%3A886&scaling=min-zoom) of the interaction using the warning button variant**~~
### Who can address the issue
<!-- What if any special expertise is required to resolve this issue? -->
### Other links/references
<!-- E.g. related GitLab issues/MRs -->BacklogDennis TangDennis Tanghttps://gitlab.com/gitlab-org/gitlab/-/issues/225300Pipeline is very slow and sometimes not started showing pending.It was workin...2020-08-06T13:39:27ZarunkumarPipeline is very slow and sometimes not started showing pending.It was working fine till thenBefore raising an issue to the GitLab issue tracker, please read through our guide for finding help to determine the best place to post:
* https://about.gitlab.com/getting-help/
If you are experiencing an issue when using GitLab.com, y...Before raising an issue to the GitLab issue tracker, please read through our guide for finding help to determine the best place to post:
* https://about.gitlab.com/getting-help/
If you are experiencing an issue when using GitLab.com, your first port of call should be the Community Forum. Your issue may have already been reported there by another user. Please check:
* https://forum.gitlab.com/
If you feel that your issue can be categorized as a reproducible bug or a feature proposal, please use one of the issue templates provided and include as much information as possible.
Thank you for helping to make GitLab a better product.https://gitlab.com/gitlab-org/gitlab/-/issues/225276An error occurred while fetching folder content2021-06-07T12:30:30ZRoby JoseAn error occurred while fetching folder contentThis issue is similar to #36864 (https://gitlab.com/gitlab-org/gitlab/-/issues/36864#note_370428500)
It says the issue is closed but I am not sure if this was resolved? hence raising again.
I am located in Brisbane Australia. For the pa...This issue is similar to #36864 (https://gitlab.com/gitlab-org/gitlab/-/issues/36864#note_370428500)
It says the issue is closed but I am not sure if this was resolved? hence raising again.
I am located in Brisbane Australia. For the past few weeks while browsing the project dashboard on my PC I get this message "An error occurred while fetching folder content". Al my projects on all browsers I tried (Chrome, Edge, Firefox)face the same issue. Clearing browsing data or going incognito did not help.
Each time I try login I get this warning email "Your git account was signed in to from a new location". I don't have this issue when I use a browser on my Mac though. The VPN clients on PC (Forticlient) and Mac(Cisco AnyConnect) are different, can this be a reason?https://gitlab.com/gitlab-org/gitlab/-/issues/224664AutoStop Environments cron job intermittently fails2020-06-30T14:46:08ZIvan BazaychenkoAutoStop Environments cron job intermittently fails<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "regression" or "bug" label:
- https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression
- https://gitlab....<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "regression" or "bug" label:
- https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression
- https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=bug
and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
We're using self-hosted gitlab and getting intermittent error with Environments AutoStop. CI pipeline was configured as described here
https://docs.gitlab.com/ee/ci/environments/index.html#auto-stop-example
Also we use it as part of Upstream job, Main pipeline triggers second pipeline which creates Dynamic env and set the auto stop parameter
```environment:
name: "$env_name"
url: $DYNAMIC_ENV_URL
on_stop: DestroyStack
auto_stop_in: 180 minutes
```
### Steps to reproduce
Create the main pipeline which triggers upstream project. In upstream project pipeline set a dynamic env in stage definition, set the on_stop parameter with next stage which destroys environment and stops it in gitlab.
### Example Project
### What is the current *bug* behavior?
on_stop intermittently fails and doesnt trigger dependent stage for deleting\stopping environment.
### What is the expected *correct* behavior?
All Dynamic environments are stopped and stage triggered successfully.
### Relevant logs and/or screenshots
Checked sidekiq logs and getting this error
```
{"severity":"WARN","time":"2020-06-26T01:24:28.059Z","error_class":"NoMethodError","error_message":"undefined method `track_error' for Gitlab::ErrorTracking:Module\nDid you mean? track_exception","context":"Job raised exception","jobstr":"{\"queue\":\"cronjob:environments_auto_stop_cron\",\"args\":[],\"class\":\"Environments::AutoStopCronWorker\",\"retry\":false,\"queue_namespace\":\"cronjob\",\"jid\":\"1aa41e4f4d5d83a4c755ccea\",\"created_at\":1593134666.4877043,\"correlation_id\":\"c1854db645ed774b8d81a781f3a20e09\",\"enqueued_at\":1593134666.4890296}","queue":"cronjob:environments_auto_stop_cron","args":[],"class":"Environments::AutoStopCronWorker","retry":false,"queue_namespace":"cronjob","jid":"1aa41e4f4d5d83a4c755ccea","created_at":"2020-06-26T01:24:26.487Z","correlation_id":"c1854db645ed774b8d81a781f3a20e09","enqueued_at":"2020-06-26T01:24:26.489Z","error_backtrace":["app/services/ci/stop_environments_service.rb:31:in `rescue in block in execute_in_batch'","app/services/ci/stop_environments_service.rb:29:in `block in execute_in_batch'","app/services/ci/stop_environments_service.rb:28:in `execute_in_batch'","app/services/environments/auto_stop_service.rb:35:in `stop_in_batch'","app/services/environments/auto_stop_service.rb:23:in `block (2 levels) in execute'","lib/gitlab/loop_helpers.rb:16:in `block in loop_until'","lib/gitlab/loop_helpers.rb:15:in `times'","lib/gitlab/loop_helpers.rb:15:in `loop_until'","app/services/environments/auto_stop_service.rb:22:in `block in execute'","lib/gitlab/exclusive_lease_helpers.rb:29:in `in_lock'","app/services/environments/auto_stop_service.rb:21:in `execute'","app/workers/environments/auto_stop_cron_worker.rb:13:in `perform'","lib/gitlab/application_context.rb:46:in `block in use'","lib/gitlab/application_context.rb:46:in `use'","lib/gitlab/with_request_store.rb:7:in `with_request_store'","lib/gitlab/sidekiq_daemon/monitor.rb:49:in `within_job'"]}
```
### Output of checks
#### Results of GitLab environment info
<details>
<summary>Expand for output related to GitLab environment info</summary>
<pre>
System information
System: Ubuntu 18.04
Proxy: no
Current User: git
Using RVM: no
Ruby Version: 2.6.5p114
Gem Version: 2.7.10
Bundler Version:1.17.3
Rake Version: 12.3.3
Redis Version: 5.0.7
Git Version: 2.24.1
Sidekiq Version:5.2.7
Go Version: unknown
GitLab information
Version: 12.9.2-ee
Revision: 0ad76f4d374
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: PostgreSQL
DB Version: 10.12
Elasticsearch: no
Geo: no
Using LDAP: no
Using Omniauth: yes
Omniauth Providers: azure_oauth2
GitLab Shell
Version: 12.0.0
Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories
GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell
Git: /opt/gitlab/embedded/bin/git
</pre>
</details>
#### Results of GitLab application Check
<details>
<summary>Expand for output related to the GitLab application check</summary>
<pre>
GitLab Shell: ... GitLab Shell version >= 12.0.0 ? ... OK (12.0.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Internal API available: OK
Redis available via internal API: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Gitaly ...
Gitaly: ... default ... OK
Checking Gitaly ... Finished
Checking Sidekiq ...
Sidekiq: ... Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Incoming Email ...
Incoming Email: ... Reply by email is disabled in config/gitlab.yml
Checking Incoming Email ... Finished
Checking LDAP ...
LDAP: ... LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab App ...
Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Redis version >= 2.8.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.6.5)
Git version >= 2.22.0 ? ... yes (2.24.1)
Git user has default SSH configuration? ... yes
Active users: ... 369
Is authorized keys file accessible? ... yes
Elasticsearch version 5.6 - 6.x? ... skipped (elasticsearch is disabled)
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished
</pre>
</details>
### Possible fixeshttps://gitlab.com/gitlab-org/gitlab/-/issues/223435Creating an Issue with multiple /label commands doesn't add all of the labels...2021-02-11T15:25:45ZRonald FindlingCreating an Issue with multiple /label commands doesn't add all of the labels to the issue (some are consistently skipped)### Summary
When creating an issue containing the `/label` command not all of the labels get added to the issue.
### Steps to reproduce
1. Create a new issue that contains several `/label` calls
2. Check the created issue and f...### Summary
When creating an issue containing the `/label` command not all of the labels get added to the issue.
### Steps to reproduce
1. Create a new issue that contains several `/label` calls
2. Check the created issue and find not all labels were added
3. For me it's reproducible that the 2 labels `Important` and `Bugfix` are not added
<!--
### Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)
-->
### What is the current *bug* behavior?
Some of the labels are not assigned to the issue instead the `/label ~"MyLabel"` stays in the issue description
### What is the expected *correct* behavior?
The `\label ~"MyLabel"` gets removed and `MyLabel` gets assigned to the issue
### Relevant logs and/or screenshots
The Issue Content:
```
Test description
**Issue Type**
Bugfix
/label ~"Bugfix"
**Issue Priority**
Important
/label ~"Important"
It is important because of reasons
**Bugfix**
What steps will reproduce the issue ?
1. Test 1
What are the impacts of this bug ?
1. another test
**Requirements**
- [ ] Test must be closed afterwards
**Rough Issue Size**
My gut feeling says that this will probably take around `1h`
/label ~"Tech Backlog"
/label ~"Whoop!"
```
The resulting issue
![Test_Issue___2074____Issues___smec___smec-services___GitLab](/uploads/61d250898690a9e4b4841d77d02992aa/Test_Issue___2074____Issues___smec___smec-services___GitLab.png)
The expected issue
![Manipulated_Test_Issue___2079____Issues___smec___smec-services___GitLab](/uploads/d1ebc0373e5c6c314b946598278edd7b/Manipulated_Test_Issue___2079____Issues___smec___smec-services___GitLab.png)
Assigned label
![Labels___smec___smec-services___GitLab](/uploads/1a36ac6a95da5ee3b24df937ee1a2cbc/Labels___smec___smec-services___GitLab.png)
Not assigned label
![Labels___smec___smec-services___GitLab](/uploads/6458dfefb3abb2dd2f22b9067d00cb0b/Labels___smec___smec-services___GitLab.png)
Our gitlab version: `GitLab Enterprise Edition 12.10.6-ee`
<!--
### Output of checks
Bug observed on our own gitlab instance.
#### Results of GitLab environment info
<details>
<summary>Expand for output related to GitLab environment info</summary>
<pre>
(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)
(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
</pre>
</details>
#### Results of GitLab application Check
<details>
<summary>Expand for output related to the GitLab application check</summary>
<pre>
(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:check SANITIZE=true`)
(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`)
(we will only investigate if the tests are passing)
</pre>
</details>
### Possible fixes
-->
/label ~bug https://gitlab.com/gitlab-org/gitlab/-/issues/223132JUnit report is not showing my tests2024-01-30T00:14:00ZTim HiseJUnit report is not showing my tests### Summary
After enabling the [JUnit reporting for pipelines feature](https://docs.gitlab.com/ee/ci/junit_test_reports.html#how-it-works), and pointing the artifacts.reports.junit at the xml being generated, I still fail to see test su...### Summary
After enabling the [JUnit reporting for pipelines feature](https://docs.gitlab.com/ee/ci/junit_test_reports.html#how-it-works), and pointing the artifacts.reports.junit at the xml being generated, I still fail to see test summary either on the merge requests or in the pipelines pages. In pipelines, we see the new tests tab but it simply says "There are no tests to show." We can see that the artifact uploaded properly.
### Steps to reproduce
Run a merge request pipeline with it configured to output a junit test report and be sure that you set artifacts.reports.junit to the path of the generated file.
### What is the current *bug* behavior?
Tests tab in pipelines simply shows "There are no tests to show."
### What is the expected *correct* behavior?
A test summary shows
### Relevant logs and/or screenshots
Here is a sample of the generated tests file that is uploaded.
![Screen_Shot_2020-06-18_at_2.29.17_PM](/uploads/a97b8e8ef9f7d754f84b62691de564e7/Screen_Shot_2020-06-18_at_2.29.17_PM.png)
### Output of checks
This bug happens on a hosted instance of GitlabBackloghttps://gitlab.com/gitlab-org/gitlab/-/issues/222355Two Builds are triggered for one merge request.2020-12-07T16:30:27ZRakesh ChaudhariTwo Builds are triggered for one merge request.![build](/uploads/8b4dd8827ec8f434e8c0988e4602fc25/build.PNG)
I have checked integration, it works perfect most of the time but when once two build are triggred back to back then preceding on each merge the 2x-build are triggered.
I have...![build](/uploads/8b4dd8827ec8f434e8c0988e4602fc25/build.PNG)
I have checked integration, it works perfect most of the time but when once two build are triggred back to back then preceding on each merge the 2x-build are triggered.
I have tried with re-configuring the integration section twice.https://gitlab.com/gitlab-org/gitlab/-/issues/222263Right Side Name ToDo Bar responsiveness issue2020-06-17T11:07:26ZMuhammad MohtashamRight Side Name ToDo Bar responsiveness issueRight side baar responsiveness not working properly means if we want to select more option that shown in below there is no
option to scroll up or scroll down to select other options, even that more options is available in bottom of sid...Right side baar responsiveness not working properly means if we want to select more option that shown in below there is no
option to scroll up or scroll down to select other options, even that more options is available in bottom of side bar.
This side bar shows when we in the project/repository and select the issues option to open new issue.
screen shots are given.
![gitBug](/uploads/7eb21a8e96b8f66001781a85db4a842a/gitBug.PNG)
![gitBug2](/uploads/bd264bb2a4376d609405d273d1b452b3/gitBug2.PNG)https://gitlab.com/gitlab-org/gitlab/-/issues/221284Feedback on Iterations MVC / Where you'd like to see us go next2022-02-25T15:21:11ZGabe Weavergweaver@gitlab.comFeedback on Iterations MVC / Where you'd like to see us go nextWe launched Iterations in %13.2 and have a lot of ideas for where we could next -- https://gitlab.com/groups/gitlab-org/-/epics/2422#mvc-user-flow -- which include things like automatically calculating team velocity/volatility, auto-sche...We launched Iterations in %13.2 and have a lot of ideas for where we could next -- https://gitlab.com/groups/gitlab-org/-/epics/2422#mvc-user-flow -- which include things like automatically calculating team velocity/volatility, auto-scheduling iterations, automatically moving issues from one iteration to the next, surfacing iteration data on Issue Boards, and more.
What's the next thing we can add to Iterations to help your team schedule/plan work more effectively?https://gitlab.com/gitlab-org/gitlab/-/issues/220260CI - Pipeline with no jobs is failing2024-02-16T00:20:45ZNameer P KCI - Pipeline with no jobs is failingI have, say, two jobs `script1` and `script2` in `.gitlab-ci.yml`. `script1` runs whenever there is a change in the directory `script1`; likewise `script2`.
Take a look at the file:
```yaml
script1:
only...I have, say, two jobs `script1` and `script2` in `.gitlab-ci.yml`. `script1` runs whenever there is a change in the directory `script1`; likewise `script2`.
Take a look at the file:
```yaml
script1:
only:
refs:
- merge_requests
- master
changes:
- script1/**/*
script: echo 'script1 done'
script2:
only:
refs:
- merge_requests
- master
changes:
- script2/**/*
script: echo 'script2 done'
```
The job(s) is/are succeeding as expected for a change in `script1`, a change in `script2`, and change in both the directories. But when there is no change in either directory, the pipeline is failing.
In the overview, Gitlab gives the message
`Could not retrieve the pipeline status. For troubleshooting steps, read the `<a href="https://gitlab.com/help/user/project/merge_requests/reviewing_and_managing_merge_requests.md#troubleshooting">`documentation`</a>`.`
[![Overview SS][1]][1]
In the `Pipelines` tab, I have the option `Run pipeline`, clicking on which gives the error
`An error occurred while trying to run a new pipeline for this Merge Request.`
[![Pipelines SS][2]][2]
[1]: https://i.stack.imgur.com/Eq7Iy.png
[2]: https://i.stack.imgur.com/6TzAp.pngBackloghttps://gitlab.com/gitlab-org/gitlab/-/issues/220142Unable to add gitlab repo as vcs url in bintray jcenter. Getting 4042021-06-25T10:36:13ZHemanthUnable to add gitlab repo as vcs url in bintray jcenter. Getting 404### Summary
Unable to add gitlab repo as vcs url and link to bintray's jcenter repository. Getting 404.
### Steps to reproduce
1. Create a public gitlab repository
2. Create a bintray repository
3. Create a bintray package. While crea...### Summary
Unable to add gitlab repo as vcs url and link to bintray's jcenter repository. Getting 404.
### Steps to reproduce
1. Create a public gitlab repository
2. Create a bintray repository
3. Create a bintray package. While creating the package, provide your vcs url link. (https://gitlab.com/hemanthsridhar/framework-utilities.git)
4. Publish your maven package.
5. Click on add to jcenter
6. Click on send
7. You will get an error message, 404 the link does not exist.
Bintray Package : https://bintray.com/hemanthsridhar/checksum-test/testing
**IMPORTANT NOTE: Also contacted bintray support and they responded that they get 403 forbidden when accessing the url.**
![Screenshot_2020-06-03_at_2.01.08_PM](/uploads/07f43e4e958220b45411ab0ebfa202fa/Screenshot_2020-06-03_at_2.01.08_PM.png)https://gitlab.com/gitlab-org/gitlab/-/issues/220129After migration, the new address jumps back to the old address2020-06-04T02:04:22ZChen Biao Ning EnglorymediaAfter migration, the new address jumps back to the old addressAfter the gitlab migration, the domain name redirection problem, the old machine domain name www.a.com new machine domain name www.b.com, access to the new machine domain name /, directly redirected to the old machine domain name login, ...After the gitlab migration, the domain name redirection problem, the old machine domain name www.a.com new machine domain name www.b.com, access to the new machine domain name /, directly redirected to the old machine domain name login, resulting in the normal access to the new gitlab address , If you want to access the new one, you need to add /user behind the domain name to access normally.
gitlab version 12.4.1https://gitlab.com/gitlab-org/gitlab/-/issues/219409Add Webhook logger to log all executions in addition to errors2024-03-11T06:23:39ZChris DenneenAdd Webhook logger to log all executions in addition to errors<details>
<summary>Click to read the original issue description</summary>
Currently running GitLab 12.9.3 (but don't see any bugfix for this issue in later versions).
I have many repos setup with Webhooks. I cannot however find any log...<details>
<summary>Click to read the original issue description</summary>
Currently running GitLab 12.9.3 (but don't see any bugfix for this issue in later versions).
I have many repos setup with Webhooks. I cannot however find any logging in any log files for the webhook actually being kicked off (successful or unsuccessful).
I'm seeing very inconsistent results on the downstream system that makes me believe it "sometimes" is working but can't find any consistency to this claim.
Can someone tell me where this info might be logged?
Also is there a way to troubleshoot why certain branch creations (enabled for Push Events) are triggering the webhook but others might not be?
~bug ~"Category:Integrations" ~"Accepting merge requests" ~webhooks ~"devops::create"
</details>
### About
We don't currently log webhook executions.
We [log webhook execution errors](https://gitlab.com/gitlab-org/gitlab/-/blob/1b956a6ea5048d999e8184656b55319cb79a86a1/app/services/web_hook_service.rb#L91) to `application`. Rate limit errors and recursion detection errors are logged to `auth.log`, which [may be the correct place](https://docs.gitlab.com/ee/administration/logs.html#authlog) to continue logging them.
### Proposal
Add a new webhook logger file https://docs.gitlab.com/ee/administration/logs.html (for example `webhooks_json`).
Log all executions and execution errors to this file.
Note, rate limit errors and recursion detection errors could still go to `auth.log`, as [it's documented](https://docs.gitlab.com/ee/administration/logs.html#authlog) as a place that logs rate limits "of raw endpoints". But we should decide if these types of webhook errors should continue to be logged in `auth.log` or if they should be logged into the new webhook logs file.
We should document the new file in https://docs.gitlab.com/ee/administration/logs.html and update any webhook docs that mention the old location of logs.
Note: Because there can be a lot of webhook executions we should double-check what the impact of increasing the logging of webhook execution might be.Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/219307Ability to restrict running manual gitlab-ci tasks to specific users2024-02-23T13:28:46ZFurkan TĆ¼rkalAbility to restrict running manual gitlab-ci tasks to specific users### Problem to solve
Like this [issue](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/21809), but for users.
### User experience goal
Only specific given users (usernames) able to run manual actions whom have necessary accesses on...### Problem to solve
Like this [issue](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/21809), but for users.
### User experience goal
Only specific given users (usernames) able to run manual actions whom have necessary accesses on `gitlab-ci.yaml`.
### Proposal
```
deploy_production:
stage: deploy
script:
- echo "Deploy to production"
when: manual
only:
users:
- maintainer2
- maintainer4
```
### Further details
We can not combine with the `roles`.
`maintainer`: (rule)
* *(maintainer)* maintainer1
* *(maintainer)* maintainer2 (only this user can make deploy)
* *(maintainer)* maintainer3
* *(maintainer)* maintainer4 (only this user can make deploy)
If we use:
```
roles:
- maintainer
```
...then it should be override users sections and should warn us something like: "Hey, you're trying to override roles over users!"
Waiting for your thoughts. :)https://gitlab.com/gitlab-org/gitlab/-/issues/219254Count the number of usages via api2020-05-29T10:05:38ZEugeneCount the number of usages via apiThereās a project on gitlab - a script. Is there any way how I can count the quantity of users who have been using the script? May this information be obtained via gitlab api?Thereās a project on gitlab - a script. Is there any way how I can count the quantity of users who have been using the script? May this information be obtained via gitlab api?https://gitlab.com/gitlab-org/gitlab/-/issues/218736Artefacts noch displayed when using license_compliance2020-05-30T03:21:57ZRene KochArtefacts noch displayed when using license_complianceI am using the gitlab-ci system in my project for licence compliance. I got the example from the list and just remove the restriction from branches, so it will run in my master branch and pipeline.
Even with having a few issues with a p...I am using the gitlab-ci system in my project for licence compliance. I got the example from the list and just remove the restriction from branches, so it will run in my master branch and pipeline.
Even with having a few issues with a private nuget registry, the pipeline and job says passed.
The last information is:
gl-license-scanning-report.json: found 1 matching files
Uploading artifacts to coordinator... ok id=299 responseStatus=201 Created token=WyQCqVqP
But within gitlab gui there is no way to download it. No download button, no artefact shown.
![image](/uploads/9ab4ce5a8d1bd95afdba90d56ad0f528/image.png)
Is this because I use gitlab-CE and this is a EE feature only?
How can I see EE-Features?
On this page:
https://docs.gitlab.com/ce/user/compliance/license_compliance/index.html
There is only "ultimate gold" sign, but isnt CE CE and EE EE?